> hmmm..so correct me if its not the right understanding..i.e. the only time
> wicket would be fetching the older page versions is when a user hit the back
> button and clicks on a link (or submit a form) from that previous page, and
> with that whatever page-version those links/forms were linked t
-----------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Second-Level-Cache-tf4824369.html#a13816327
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> Well i think it is required, at least as far as the browser back button is
> concerned (which is one of the features of wicket i.e. "back button
> support"), unless otherwise as you said where one explicitly wants to make a
> call to the old versions
You don't need to do roundtrips right away. I
a call back to that page (such as
> a link or form submit). And those call backs will have the version
> info in them.
>
> Eelco
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands,
On Nov 17, 2007 4:58 PM, mfs <[EMAIL PROTECTED]> wrote:
>
> So basically i meant setting "no-store" in your response header so that the
> browser doesnt load the page from its local-cache, and instead sends the
> request to the server and let wicket load the last serialized page.
I don't think it
ail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Second-Level-Cache-tf4824369.html#a13815263
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> I understand that the browser back button doesnt really come in the above
> context, but you agree to the fact that one has to do a no-store to actually
> LET wicket load the page from the SLC otherwise this back button support by
> wicket (which is considered to be one of the main features of it
gt;> I am yet bringing the same question again, regarding the SLCSS and the
>> need
>> to maintain it the older versions of the page on the disk or
>> otherwise...and
>> would really appreciate if some of my questions could be addressed here..
>>
>> Before i
When user presses the back button, wicket need to reconstruct the
previous page instance. And the previous page instance is stored in
second level cache. Wichet is a statefull framework, it maintains page
instances. Most of the time the url only contains page id and page
version. This is used to
> to maintain it the older versions of the page on the disk or
> otherwise...and
> would really appreciate if some of my questions could be addressed here..
>
> Before i go into Second Level Cache..i would say that i still can
> comprehend
> the reason to store the latest version of
Guys,
I am yet bringing the same question again, regarding the SLCSS and the need
to maintain it the older versions of the page on the disk or otherwise...and
would really appreciate if some of my questions could be addressed here..
Before i go into Second Level Cache..i would say that i still
11 matches
Mail list logo
