[Seaside] Back button question

itsme213 itsme213 at hotmail.com
Wed Jul 23 22:43:45 UTC 2008

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: 

  html anchor
    callback: [self isolate: [WARenderLoop new call: self]]
    with: 'Explicit Refresh'

Other suggestions?

Thanks - Sophie

More information about the seaside mailing list