[Seaside] getting to the state of the previous continuation

Julian Fitzell jfitzell at gmail.com
Wed Jun 9 10:21:58 UTC 2010

Hi Johan,

That sounds a bit strange. We don't currently maintain back pointers
to the previous continuation - I suppose we could consider doing so as
long as they were weak references (so they can still expire from the
cache and get GC'ed). Perhaps that's the approach you should take in
your subclassed continuations?

If you are able to elaborate a bit more on what you're trying to
accomplish I might have a higher level idea for a good approach, but
from what you've said, subclassing the continuations to maintain a
weak back pointer seems like the best solution.


On Tue, Jun 8, 2010 at 3:41 PM, Johan Brichau
<Johan.Brichau at uclouvain.be> wrote:
> Hi everyone,
> I'm trying to do some exotic stuff for which I need access to the state of the components in the continuation that precedes the currently rendering Seaside continuation.
> So basically: I want to know if there is a way to get to the WASnapshot instance that captures the component states for the page that was previously rendered.
> I'm currently looking at getting the _k parameter from the referer url in the request and using that to get the continuation from the continuations dictionary in the session. However, it seems a bit of a detour... so would there be a better way to do that?
> I know, it's not something you normally want to do in a Seaside application.... I'm actually trying to implement a new renderphasecontinuation that needs this information from its precedessor...
> ----------------------------
> Johan Brichau
> johan.brichau at uclouvain.be
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list