If you have a serializable object, tapestry can serialize an object
into a very long string. This is not usually desirable. I wrote a
custom squeezer a while back for an object that was the only
practical way to pass certain data around. It was worth it. It ended
up being around 20 characters or so in the URL--until we added some
more fields and it grew over 30 or so. Still that's way better than
the hundreds we got with plain serialization.
Jamie
On Sep 27, 2005, at 6:47 PM, Ron Piterman wrote:
Hi,
I have a class for which I would like to write a custom squeezer.
The class also implements serializable.
Is it possible to use a custom squeezer, or will tapestry first use
the serializable one?
Cheers,
Ron
---------------------------------------------------------------------
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]
