Do not get into encoding and decoding....as you might be aware that you can
specify the charset at many places like web.xml, in javascript tag and also
when you encode/decode in java. This means that decoding result can be
different from what you expect if a different charset is used...It might solve
your problem in short run ...
So a good idea to avoid it if you can
Regards
-----Original Message-----
From: Dave Newton [mailto:[EMAIL PROTECTED]
Sent: 09 June 2006 14:06
To: Struts Users Mailing List
Subject: Re: best way to send parameters through more requests
Emilia Ipate wrote:
> Now the question comes: when does the object come useless? It is useless
> when users gets to step 5 and also when from a middle step (like 3)
> decides to get out of the this 5 step request-chain. In both cases, the
> object should be removed from session. I would say to have a
> configuration file that says for which url-patterns request should the
> object be kept in the session. So, when another request (which is not
> part of the url-patterns) comes in, the filter will remove the object
> from session!
>
> What do you think?
I think that's not worth the effort.
> What else I could do to make sure the session does
> not become too big? Encode64 sounded like a good idea.
>
Huh? That would make binary data _bigger_, not smaller, unless you then
zipped it, which seems... silly.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
