[Seaside] Re: Comet timeouts with 403 forbidden
tamackinnon at gmail.com
Wed Aug 18 19:26:59 UTC 2010
Kai-Uwe Pielka <webmail at pielka.de> wrote:
> I remember that I also had Some Trouble to Run a Timer and Comet in
> parallel. I think the Problem was that Some Browsers only allow two
> parallel Connections with the Server at the Same Time.
Good point - I recalled that figure from the past, but I did a check and
it seems my FF should allow 6 (of course it still might be this). Most
pages seem to quote:
Browser HTTP/1.1 HTTP/1.0
IE 6,7 2 4
IE 8 6 6
Firefox 2 2 8
Firefox 3 6 6
Safari 3,4 4 4
Chrome 1,2 6 ?
Chrome 3 4 4
Opera 9.63,10.00alpha 4 4
It's very mysterious - there is so much to learn. When I figure it out
(if ever?) will note it on the seaside book.
> Am 18.08.2010 um 13:42 schrieb TimM <tamackinnon at gmail.com>:
>> Lukas Renggli wrote:
>>> You can find some pointers in JQAllFunctionalTest>>#renderTimeoutOn:
>> Hey thanks - I found the bit of code, however I can't seem to get it
> > to work with comet?
>> As a test, I added the following to my renderOn: method -
>> html document
>> addLoadScript: (html jQuery ajax
>> callback: [ Transcript cr; show: 'keep the session active' ];
>> interval: 10 seconds).
>> If I disable comet, I get a message every 10 seonds, with comet - I
> > get nothing?
>> Thinking about it - should comet keep the session open anyway? But
> > then why after a little while does my app stop working - and I see
> > 403 forbidden messages in firebug...
>> Its all a bit strange (its worth saying that this is on a mac,
> > running locally with Kom - does that have some bearing)?
>> Again - tips appreciated.
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
More information about the seaside