From: "Lee Harrington" <[EMAIL PROTECTED]>
> What's the best strategy for avoiding "last save wins" concurrency
> issues? If two people open a web maintenance page, change data, and
> save, the "last saved" wins, meaning the person who saved first loses
> their changes.
I don't claim that it's b
ers Mailing List"
To: Struts Users Mailing List
cc: (bcc: Glenn Deschenes/NAT/CMHC-SCHL/CA)
Subject:OT: Handling concurrency issues with web apps
Classification:
Ok...here's a general development issue that conerns any web based app
that is
Ok...here's a general development issue that conerns any web based app
that is data entry oriented. I've been doing reporting systems so
long, I've gotten a bit rusty with transactional development.
What's the best strategy for avoiding "last save wins" concurrency
issues? If two people open a w
3 matches
Mail list logo
