On Wed, Feb 06, 2002 at 03:02:15PM -0000, simon wrote: > This is application-independant, in that it's not just struts this affects
Correct. > One solution is to look for potential collisions and implement a lease/lock > strategy on the resources that my collide (similar to std. file/resource > locking), although with a lease on the lock due to the stateless nature of > the app. in question. Hmm, but what to do with true session data like a "current project" or "current view" bean. This could also be placed into a form as hidden data, but why should I use the session scope at all then? > When I've had problems where multiple users edit the same data, I've > generally taken the easy option and decided that the users have to have at > least an iota of sense and collaberate with each other. This is also our strategy: users should cooperate, last update wins, business logic must assert consistency of its data. Unfortunately, this does not solve my "multiple browsers in single session" problem. Erich -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
