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 wrote:
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 state.
This key can be safely client persisted as it will not be too long. If
you use a WeakHashMap or some kind of expiry strategy with the
database, then you don't have to concern yourself too greatly with
filling up with stale data.
Hope that gives you a pointer
Richard
[EMAIL PROTECTED] wrote:
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!
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 on to the results page. The results page
contains only a table which renders itself dynamically (that is,
columns are added as needed depending on what kind of object is
obtained from the ids) and can be paginated. Those ids are stored in
a property and it was set to persist="client". However, we found out
that it wouldn't work with larger result sets. So we set it to
persist="session". This created a small issue, which is: if the user
opens a new window (hitting CTRL-N, for example) and performs a new
search, and then returns to the previous window and paginates, he
finds himself navigating the results of the new search. That is, we
lost the capability of 'forking' (sorry, couldn't find a different
way to express myself) we used to have with persist="client". Has
anyone got any idea for solving this issue?
Thank you!
Greetings
Rodrigo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu
celular. Registre seu aparelho agora!
---------------------------------------------------------------------
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]
