Hi Rodrigo again,
Umm, actually you should just need to generate a new key each time the
search form is submitted for a new search.
Cheers
Richard
Richard Kirby wrote:
Hi Rodrigo,
What you will need to do is ensure that caching is disabled for the
pages that use this key idea. Then CTRL-N
Hi Rodrigo,
What you will need to do is ensure that caching is disabled for the
pages that use this key idea. Then CTRL-N or File | New Window should
cause the browser to refresh from the server - they will request the
same url as the original page, so that allows you to detect that a new
key
Hi Richard!
Thank you for your reply. It sounds like a very good solution to my
problem.
However, I can't find out a way to generate a new key when the user hits
CTRL-N or clicks 'File | New Window' and a new window is open. Any ideas?
Thanks a lot in advance!
Rodrigo
Richard Kirby wr
Hi Rodnei and Rodrigo,
Browsers have an upper limit on url lengths, so as you have found, using
the client persistence strategy can easily hit this limit. One possible
solution is instead to store your state in a database or even a Map at
the server, and use a random number as a key to this st
Hi...
I have a similiar problem, and i haven't solved it yet... my question is how
to
have client properties that have more than 4000 characters... or anything
equivalent...
Can anyone help me, please?
[]'s
Rodnei Couto
Rodrigo Barberá <[EMAIL PROTECTED]> escreveu:
Hello!
Hello!
There is this little problem, if I can even call it a problem, I'd like
help to find a solution to. My Tapestry 4.0 application basically
consists of two pages. One contains a form in which the user can enter
search parameters. This page executes the query and passes the object
ids