Thiago H. de Paula Figueiredo schrieb:
>> ValueEncoder does not need streamed data if it can obtain the object
>> from an identifier. But the data I am using is not stored anywhere so
>> the only way I see is streaming the data and reconstructing the objects.
>> Currently I am using Xstream for this.
> In your case, isn't serializing and deserializing objects all the time
> worse than keeping them in the session?
Keeping the data in the session would break tabbed browsing.
The page I am talking about it for administrators only, so load and
traffic are not the problem here.
> And don't forget that most browsers don't accept very long URLs. I
> don't know their URL limit, though.
That's why I wanted to use hidden fields in my form.
>> Form submission is the way I want it to do. The passed values should be
>> stored in a Hidden-component so that they are submitted with the form.
> I've just tested and read the sources of the client persistence,
> something I've never used before. :)
Thank you for your effort. :)
> @Persist works in a single page. Thus, as long as you stay in the same
> page, @Persist("client") works when you submit a form (Tapestry
> automatically adds the hidden field) and even in links that point to
> the same page (including event URLs).
It is the same page, sorry if my first mail was misleading. But IIRC the
setting @Persist("client") produced URL parameters instead of hidden
fields. How can I force the latter?
Regards
Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
