Well, we will probably head into clustering some day. What pattern,
then, can we use to do optimistic locking without hibernate "long
conversations"? I don't think session-per-request can do it.
bill
On 4/3/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
My problem with session-per-conversat
My problem with session-per-conversation is that its totally
incompatible with clustering, since the objects in the detached
session are not propogated to other servers.
That being said; yes some kind of mechanism (as service, an ASO) to
hold onto the sessions between requests, to support detach
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()
