Has anyone implemented session-per-conversation (my preferred way to
handle optimistic locking) in T5? Right now, tapestry-hibernate
implements session-per-request.
I'm thinking an application state object is a good place to start here
with methods like startConversation() and endConversation() with
hibernate sessions managed by this service.
Any thoughts?
Bill
--
"The future is here. It's just not evenly distributed yet."
-- Traditional
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
