[Seaside] Re: Comet timeouts with 403 forbidden
TimM
tamackinnon at gmail.com
Wed Aug 18 20:34:03 UTC 2010
Lukas Renggli <renggli at gmail.com> wrote:
> I changed the comet implementation a bit so that it makes sure that
> whenever a session successfully pushes some data it also notifies the
> cache. This should make everything simpler and there is no refresh or
> background request necessary. I haven't tested it deeply, but it
> should basically work:
Hey thanks Lukas - I'll try it out and add to the manual testing at
least. I'm also keen to see what you did.
Tim
>
> Name: Comet-Core-lr.51
> Author: lr
> Time: 18 August 2010, 10:20:27 pm
> UUID: 35503206-5565-43ad-8c44-48f70c510a49
> Ancestors: Comet-Core-obi.50
>
> - made sure that sessions that push through a comet handler do not
> timeout
>
> On 18 August 2010 22:01, TimM <tamackinnon at gmail.com> wrote:
>> 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.
>>>
>>
>> In reading up in how other languages do this, a few things came up
> > for
>> me to try:
>>
>> 1) just send some noop script from the server so that clients keep
> > their
>> connection open
>> 2) check if seaside comet propagates a timeout exception and than use
>> that to request a page reload or rerequest the long poll
>>
>> Worth a shot I guess
>>
>> Tim
>>
>>>
>>> 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.
>>>>
>>>> Tim
>>>>
>>>> _______________________________________________
>>>> seaside mailing list
>>>> seaside at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
>
More information about the seaside
mailing list