Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of markus.kohler@gmail.com
 designates 209.85.211.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=JrEBSMM91M/yQ/la1A5ZXg7aOGUjbaCHaHjCXgncQTbdvzg2e6PVMD6LAFASmcH/oy
         1UjMKwSVKY5pG+mQBqghGP9D0a3O250utB6na4t9sRQ5/9mRlHQo6RpiDEfxPoG7ealK
         VeXDiorGMz7Kx7rowhNge4U07HW021UMzsawo=
MIME-Version: 1.0
In-Reply-To: <fa2d9f450911280043v67df9524vc91ed07cdd3a7277@mail.gmail.com>
References: <771905290911280012v6ded6926i4a6f4d94aa31c0ed@mail.gmail.com>
	 <fa2d9f450911280043v67df9524vc91ed07cdd3a7277@mail.gmail.com>
Date: Sat, 28 Nov 2009 10:42:32 +0100
Message-ID: <771905290911280142g500d5d87pc612ae04e678ecea@mail.gmail.com>
Subject: Re: Incremental updates?
From: Markus Kohler <markus.kohler@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016364edd9840373204796b3a14

--0016364edd9840373204796b3a14
Content-Type: text/plain; charset=ISO-8859-1

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 <hirsch.dick@gmail.com>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 <markus.kohler@gmail.com>
> 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
> >
>

--0016364edd9840373204796b3a14--