I remember during a session of the A4D class a couple of years ago that we discussed optimistic locking. Was there any code for this that I could use? Or does anyone have any code samples for it? Looking it up, the "technical" term for it is OCC (Optimistic Concurrency Control). Wikipedia has a great article on it: http://en.wikipedia.org/wiki/Timestamp-based_concurrency_control I need a bit of assistance in understading the full process. If A then B grab the same record and B writes before A, that invalidates A's data. Is it better to:
* tell A that their data has been made invalid by another user, they must redo their operations * not let B get the record for edit at all, just read-only (not OCC, but not really locking). They would be able to edit again once we close A's session by either A loggin out or the session expiring (set to 1 hour) where we release the lock state of the record. Thanks, Michael Check _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
