[Seaside] To many liveActions on a page

[radoslav hodnicak]

The default seaside implementation of live stuff creates a new request for 
each live update (just like if you clicked a non-live link). What you see 
is the effect of the default request cache size (20) - which, in non-live 
app would mean support for going back 20 pages in browser.

The LiveWeb extension implements live updates as callbacks (within the 
current page/request), which solves this problem.

rado


On Thu, 30 Jun 2005, William E Harford wrote:

> It appears that when I have more than 20 or so live actions on a page
> seaside will expire session.
>
> Is this a known limitation ? Is there a work around? Am I doing
> something wrong ?
>
> The below is inside a loop that creates a table. When a user clicks on
> the name of a patient they are shown exam information in a div below.
>
> html anchorWithAction: []
> liveAction:[:h |
>    self showPatient: (row at: 'ionumber').
>    self renderPatientOn: h.
>    h script: 'resizeContents();removeHightlight();'.
>    h script: ' document.getElementById(''patientRow',(row at:
> 'ionumber') asString,''').className = ''active'';'.
> ] fixTemps
> text: (row at: 'lastname') .
>
> This application works well as a traditional, non-AJAX application but I
> am trying to AJAXize it almost to an extreme in order to get some idea
> of what can and can not be piratically done.
>
>
>
> -- 
> William E Harford <seaside at harford.org>
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>