On Jul 8, 2005, at 8:38 AM, t.n.a. wrote:
Todd O'Bryan wrote:
How did you handle passing CayenneDataObjects around the Tapestry
application? The squeezer just lets you use them normally, handling
serialization and deserialization behind the scenes. Before I started
using it, I had to pass around ObjectIds and such to prevent my data
objects from thinking they were in different DataContexts and
generally being a pain.
I stored the DataContext as well as most of what I needed in the
Visit.
Each user has his own visit object, each visit contains individual
DataObjects and everything seems to work just fine.
What am I missing?
I generally try to avoid putting things in the Visit and instead
store them as parameters or hidden fields in the pages. It may simply
be a misguided attempt to save memory that I'm never going to need,
but enough people have touted the holy grail of statelessness that I
guess I've bought the hype.
Todd
