[Seaside] Only the browser can have initiative to evaluateajaxian updaters?

Sebastian Sastre ssastre at seaswork.com
Sun May 27 19:20:49 UTC 2007


	I've installed Comet.mb-18.mcz package in an 3.9 image with seaside
2.7 and I see that WAListener must be used instead of WAKomEncoded39 as I'm
using for an app.
	I'm looking the counter and the chat demos. This is so good! Now I'm
enthusiasted I have  questions perhaps you can help with
	a) now that the pros are known what are the cons of Comet in Seaside
(in general)? Why you won't use Comet?
	b) is ready for production? is somebody using it in production?
	c) how can I use the WAListener and have my "normal" applications
also working
	d) how can I use Comet and the WAKomEncoded39 encodind features as
	e) an aap which uses Comet should be horizontally scaled the same
way as normal seaside applications? The techniques of Boris P. and Ramon
Leon to scale Seaside apps are still valid with Comet?


> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Lukas Renggli
> Enviado el: Domingo, 27 de Mayo de 2007 15:32
> Para: Seaside - general discussion
> Asunto: Re: [Seaside] Only the browser can have initiative to 
> evaluateajaxian updaters?
> >     Any clue on how to do it?
> Yes, this technique is called Comet.
> See this video and load the package called Comet from the 
> Seaside repository:
> http://www.lukas-renggli.ch/smalltalk/seaside/videos/comet.mov
> 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

More information about the seaside mailing list