Ok. Here is a quick explanation of the client persistent scopes and how
they work.
There is "page" and "application" scopes. defined as "client:page" and
"client:app" respectively.
Both page and application scope client-side persistence take the indicated
page values and gzip compress + base64 encode them into a single URL
parameter. This parameter is then added to every URL reference in the page
(well, to the (Page|Direct|Action|etc)Link components at least). The only
difference between the two scopes is the application scope parameter will
follow you from page to page, whereas the page scoped one will be dropped
when the page changes.
----- Original Message -----
From: "Vjeran Marcinko" <[EMAIL PROTECTED]>
To: "Tapestry users" <[email protected]>
Sent: Monday, October 03, 2005 11:12 AM
Subject: Documentation for client persistence scopes?
Hi there.
Can someone provide me with currently available client persistence scopes,
and their short explanation?
Tapestry 4.0 documentation has explicit mark that it's missing, so ...
Thanx,
Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
