Thanks!, I will check that, Markus "The best way to predict the future is to invent it" -- Alan Kay
On Sat, Nov 28, 2009 at 9:43 AM, Richard Hirsch <[email protected]>wrote: > Without being the lift/scala expert, I'd assume the following > locations might be places to start: > > scala files here: trunk\server\src\main\scala\org\apache\esme\comet > display_messages.js in trunk\server\src\main\webapp\scripts > > On Sat, Nov 28, 2009 at 9: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? > > > > Regards, > > Markus > > > > > > "The best way to predict the future is to invent it" -- Alan Kay > > >
