On 29/Sep/2010, at 1:39 PM, Mike Schrag wrote: >>>> My vote is that you are crazy. :-) This becomes an issue in apps where >>>> users concurrently edit the same object. Out of the box, it is last in >>>> wins and the second user to save gets no warning that what they are >>>> actually editing is not what they were looking at. >>> Right, but there are various ways around that. >> Which brings us back to 'implement the delegate and you get notified'. >> Perhaps not what folks would like today however it's what's there. ;-) >> M. > Miguel's still right, though. This is still kind of busted ... Just because > it's technically possible that you could implement a workaround doesn't mean > the default behavior isn't wrong. Particularly when the proposed alternative > implementation is really not simple. Yes, as the out of band conversations have shown, there are lots of ideas on how this might otherwise be. However, given 5.4.3, the delegate is the way to catch the case.
Further conversation should be tabled until the nerf bats are handed out and we have suitable drinks! ;-) M. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
