On Oct 8, 2012, at 9:54 PM, Flavio Donadio wrote: > The interface will be like in Address Book: the user opens a card/record for > viewing, but has to click an "Edit" button to make changes. If the record is > locked, the user will get an alert when he/she clicks the button. I need: > > 1. A mechanism to avoid users opening records for editing and leaving them > open "forever" (timer?);
This is not an easy problem, although I would say it is more of a business logic issue than a technical one. Namely, what would be the uncommitted data policy? Discard all changes? Or commit with a discard fallback (in case of validation errors)? Both approaches could lead to data integrity and customer service issues, depending on the business logic. In my most recent project I opted for a "social" approach: when locks are made they are "forever", but when another user tries to edit the locked row the app tells them the user that locked the record, which (hopefully) provides some action of recourse, and avoids the pitfalls I mention above. > 2. Some kind of feedback for the users when a record is unlocked, without > having to refresh manually. It shouldn't be onerous to implement a lightweight notification system--just spin off a worker thread that handles it. HTH, Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
