[Seaside] Ajax live updates

Filip Stadnik filip.stadnik at gmail.com
Tue Jul 11 07:07:15 UTC 2006

Hi Ramon,

Isn't this behaviour also associated with the nature of a web session being
processed by the server as a single thread?

Which means, the server queues subsequent requests until the very first one
is finished?

However it would make sense to have multiple parallel request being
processed in background if each one retrieved data out of a session.

Just a thought...


On 7/11/06, Ramon Leon <ramonleon at cox.net> wrote:
> > I am doing very long HTTP requests (in fact HTTP streaming) with the
> > Comet library and Scriptaculous. The latest version doesn't do any Kom
> > hacks anymore, it works by subclassing WAListener. Tough it is very
> > much work in progress, but maybe you can get some ideas from this
> > code?
> >
> > Cheers,
> > Lukas
> I'll take a look, appreciate the pointer, hopefully I'll figure
> something out.  Let me pose a question to you since you've been the
> maintainer of Scriptalicious, would you consider making all
> Scriptalicious callbacks async?  I mean what point is there in an
> asynchronous Javascript framework bound to a synchronous server?
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20060711/2127b45a/attachment-0001.htm

More information about the Seaside mailing list