Borut,
I've always stuck to the simplest approach. If I'm dealing with a
completely stateless application, I share one DataContext for all
users (in T4 as a hivemind singleton). For stateless apps, each
individual user has their own DataContext in the Visit object. I
haven't used the CayenneDataSqueezer, simply because I haven't had to
yet (though, I understand it's extremely useful).
My object entities tend to be a bit wide, so they're not something
I'd typically squeeze into a direct link for example (really long
urls can lead to undesired results w/some browsers). More often I
squeeze the object's ObjectId on actions related to specific data
objects.
Hope that helps.
Eric
On Oct 24, 2005, at 5:27 PM, Borut Bolčina wrote:
Hi,
I searched through the archives and read all that I could about
integrating Cayenne with Tapestry. The latest thread "Tapestry,
Cayenne and Squeezer" was informative, especially Filip's post
which is on wiki also. All other posts were a bit out of date I
think dealing with T3. Although reading about cayenne squeezer did
light some bulbs (ok, more of a flickering that is) I felt insecure
about how to get started.
I guess it boils down to whether you go stateless or not? In the
former case one should use ASO session scoped object (visit) and if
you want to stay stateless, than you should use all the help from
CayenneDataSqueezer. Is that correct?
Are there T4 & Cayenne (stateful, stateless or both) examples
(best practices) somewhere I missed?
Regards,
Borut
---------------------------------------------------------------------
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]
