zulip/zerver/tornado
Steve Howell 475eb21a5e Revert commits related to client_message_id.
I pushed a bunch of commits that attempted to introduce
the concept of `client_message_id` into our server, as
part of cleaning up our codepaths related to messages you
sent (both for the locally echoed case and for the host
case).

When we deployed this, we had some strange failures involving
double-echoed messages and issues advancing the pointer that appeared
related to #5779.  We didn't get to the bottom of exactly why the PR
caused havoc, but I decided there was a cleaner approach, anyway.
2017-07-14 12:13:35 -07:00
..
__init__.py tornado: Move tornado_ioloop_logging to new zerver/tornado tree. 2016-11-26 21:24:05 -08:00
application.py casper: Fix issues with server autoreloading on save. 2017-03-17 20:45:07 -07:00
descriptors.py pep8: Add compliance with rule E261 to descriptors.py. 2017-05-07 23:21:50 -07:00
event_queue.py Revert commits related to client_message_id. 2017-07-14 12:13:35 -07:00
handlers.py Django 1.11: MIDDLEWARE_CLASSES setting is deprecated. 2017-06-13 15:04:04 -07:00
ioloop_logging.py pep8: Add compliance with rule E261 to ioloop_logging.py. 2017-05-07 23:21:50 -07:00
socket.py Revert commits related to client_message_id. 2017-07-14 12:13:35 -07:00
views.py decorator: Add support for Django internal_notify_view. 2017-04-18 09:59:07 -07:00
websocket_client.py Revert commits related to client_message_id. 2017-07-14 12:13:35 -07:00