Sure we can just send the latest message, but we have to think this through. The corner cases I'm thinking about:
* if two messages arrive almost simultaneously, it's possible that they come in mixed order. This might be fine if we reorder any received message by date/id. * if someone replies to an old message, a link to the conversation would have to appear next to the message. This would be more difficult to pull off. * the javascript code for rendering the whole list of messages (display_messages.js) is currently used for non-comet stuff as well. This lets us have a common layout for timelines everywhere in ESME, regardless of whether these messages come in real-time or not. So this could work, but might have tricky parts to implement. On Sat, Nov 28, 2009 at 10:12 AM, Markus Kohler <[email protected]> wrote: > Hi all, > As far as I can see by looking into the HTTP responses with Firebug, ESME > always sends the whole list of messages back to the browser. Uncompressed > this was in my case about 43 Kbyte( haven't checked how much it is > compressed), which is significant for a single message update. > > I wonder whether there would be a way in Lift to incrementally update the > page e.g. sending only the new messages, insert them into the DOM and maybe > delete the last messages from the DOM to avoid an unlimited increase of the > browsers memory usage. > > Where could I look in the code to understand, how it is currently done?
