[Seaside] Component navigation

Philippe Marschall philippe.marschall at gmail.com
Tue Aug 30 11:29:37 UTC 2011

2011/8/29 keropotter <keropotter at gmail.com>:
> Hi!!
> I'm wondering what's the best option to navigate a series of components in
> GLASS. For instance, i'm developing a solution using anchors, and the
> callbacks use the #call: message to render the next component.
> But this makes me worry about the stack. Won't it grow indefintely and
> eventually crash my application?

No, the stacks are not joined together and only a limited set of
continuations is kept.

> I'm never giving an #answer, because I
> don't know if the user will go back to the previous component. For example,
> the user might be on one called component, and navigate via menu to another
> component that's not related to the previous one.

If you're just changing the 'main' content component then see the
answers of James and Robert.


More information about the seaside mailing list