zulip/zerver/tornado
Steve Howell 8fbb55df85 Introduce client_message_id on the server.
We are deprecating local_id/local_message_id on the Python server.
Instead of the server knowing about the client's implementation of
local id, with the message id = 9999.01 scheme, we just send the
server an opaque id to send back to us.

This commit changes the name from local_id -> client_message_id,
but it doesn't change the actual values passed yet.

The goal for client_key in future commits will be to:
    * Have it for all messages, not just locally rendered messages
    * Not have it overlap with server-side message ids.

The history behind local_id having numbers like 9999.01 is that
they are actually interim message ids and the numerical value is
used for rendering the message list when we do client-side rendering.
2017-07-13 23:42:27 -04: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 Introduce client_message_id on the server. 2017-07-13 23:42:27 -04: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 Introduce client_message_id on the server. 2017-07-13 23:42:27 -04:00
views.py decorator: Add support for Django internal_notify_view. 2017-04-18 09:59:07 -07:00
websocket_client.py Introduce client_message_id on the server. 2017-07-13 23:42:27 -04:00