[Glass] Seaside applications and System writeLock:

Trussardi Dario Romano via Glass glass at lists.gemtalksystems.com
Tue Mar 6 06:08:05 PST 2018

	i have a Seaside application and i used		 writeLock: 	to manage transaction conflicts on specific objectA.

	If the code in first session get  a	 writeLock:   objectA

	and before commitTransaction		  another  session  get  the		 writeLock: 	 on the same objectA

	how does the system behave?

		The last writeLock:  		how it behaves?

		It resubmit the request   for  some time?  how many times?

	How the Seaside framework manage this problematic?

	How i cam manage it?

	I read the GS64 Program Guide "Transaction and Concurrency Control" .

	Is the case of using Application Write Lock ?

	Thanks for considerations...


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20180306/cc9c0430/attachment.html>

More information about the Glass mailing list