[Seaside] Navigating away from call:'s

Sebastian Sastre ssastre at seaswork.com
Thu Feb 21 16:48:19 UTC 2008

Hi Ronaldo,

	yeah why not? What else do you need? It could probably it's called by a
task after a login or something like that.

	It'll mostly depend on what workflow you want/need for the site/app (for
example: a nil answer could mean a logout for the task who make the call of the
home comp.),


Sebastian Sastre

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Ronaldo Ferraz
> Enviado el: Jueves, 21 de Febrero de 2008 13:13
> Para: Seaside - general discussion
> Asunto: [Seaside] Navigating away from call:'s
> Hi,
> I've been browsing some Seaside examples (Squeak Source, this time)
> and I noticed a pattern where a call: is made replacing the current
> component with no expectation of return. For example, when navigating
> to the home page, the home component is called but it will never
> return to whatever component it's replacing. At least, that's what
> happening if I'm reading the code correctly. Is that the common way to
> handle such situations?
> -- 
> Ronaldo Ferraz
> http://log.reflectivesurface.com
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list