Hi Ramon,<br>
<br>
Isn't this behaviour also associated with the nature of a web session being processed by the server as a single thread?<br>
<br>
Which means, the server queues subsequent requests until the very first one is finished?<br>
<br>
However it would make sense to have multiple parallel request being
processed in background if each one retrieved data out of a session.<br>
<br>
Just a thought...<br>
<br>
Filip.<br><br><div><span class="gmail_quote">On 7/11/06, <b class="gmail_sendername">Ramon Leon</b> <<a href="mailto:ramonleon@cox.net">ramonleon@cox.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> I am doing very long HTTP requests (in fact HTTP streaming) with the<br>> Comet library and Scriptaculous. The latest version doesn't do any Kom<br>> hacks anymore, it works by subclassing WAListener. Tough it is very
<br>> much work in progress, but maybe you can get some ideas from this<br>> code?<br>><br>> Cheers,<br>> Lukas<br><br>I'll take a look, appreciate the pointer, hopefully I'll figure<br>something out. Let me pose a question to you since you've been the
<br>maintainer of Scriptalicious, would you consider making all<br>Scriptalicious callbacks async? I mean what point is there in an<br>asynchronous Javascript framework bound to a synchronous server?<br><br><br><br>_______________________________________________
<br>Seaside mailing list<br><a href="mailto:Seaside@lists.squeakfoundation.org">Seaside@lists.squeakfoundation.org</a><br><a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
</a><br></blockquote></div><br>