[Seaside] Comet and CTHandler>>basicTerminate

Lautaro Fernández evaklo at gmail.com
Tue Feb 17 14:13:23 UTC 2009

2009/2/17 Lukas Renggli <renggli at gmail.com>

> > Could someone (maybe Lukas) explain to me why does it need to do the
> > following lines(*) when a cometRequest is "delivered"?
> >
> > (*)CTHandler>>basicTerminate
> >     thisContext swapSender: nil.
> >     Processor activeProcess terminate
> This avoids that the stack to is unwound that that ensure blocks are
> executed.
> If that would not be done, then Seaside would generate an (empty)
> response and pass this response back to the web server. The web server
> would serialize this response onto the socket and flush and close the
> connection. These are all things that we don't want: we don't want a
> response to be created yet and we want the connection to stay open so
> that we can later stream contents to the other end. The above code
> makes that possible.

Thanks a lot Lukas. Now I understand it =D
Lautaro Fernández

> Lukas
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Luke LAut SkyFernadezWalker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20090217/a4012a12/attachment.htm

More information about the seaside mailing list