[Seaside] Back button question

Julian Fitzell julian at fitzell.ca
Thu Jul 24 02:55:45 UTC 2008

First, are you sure it's a problem? I wouldn't worry about optimizing
this until you have so many users that you're running out of

However, the simplest solution (I think) would be to subclass
WASession and implement #initialize

  super initialize.
  continuations capacity: 10.  "or however many continuations you want
to keep around"

The default capacity is 20.


On Thu, Jul 24, 2008 at 6:43 AM, itsme213 <itsme213 at hotmail.com> wrote:
> Most interaction in my app is Ajax based. Due to some Seaside 2.8
> restrictions I am using Lukas' #in:do: workaround for updating/re-rendering
> one component from the callback of another.
> This seems to cause the callback count to increase with time (at least the
> little callback numbers in Seaside generated links keep increasing)
>    _s=i178duf&_k=usj27a&45  <- 45
> OK, so I sometimes do an explicit whole-page refresh
>  html anchor
>    callback: [WARenderLoop new call: self]
>    with: 'Explicit Refresh'
> This of course enables the back button, presumably keeping around stuff that
> is meaningless for my application.
> I'm hoping for a simple way to free up at least some of the resources (e.g.
> large number of callbacks? some RenderContinuations/Contexts/or similar?)
> left around to support the back button. Is anything like isolate:
> applicable?
>  html anchor
>    callback: [self isolate: [WARenderLoop new call: self]]
>    with: 'Explicit Refresh'
> Other suggestions?
> Thanks - Sophie
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list