Hi! We currently design and implement a web application. For data persistence, we use the Torque framework from Turbine. Now we're facing the problem, that the data that is processed by the users of our webapp may be deleted (of course). Is there a best practice to solve the problem of one user deleting data that another user is using at the same time? Our current problem is, that objects that were used for building a webpage (that may contain references to these objects) might vanish a second later. I noticed some "deleted" fields in the data layout of the Scarab system. Is this part of a "dont delete things now, mark them instead and delete them offline later"-strategy? This might have the advantage, that the object references (i.e. primary keys hidden in webpages) will remain valid. Are there other solutions to this problem? How do other people solve this? Thanks in advance, Erich -- Dr. Erich Meier, Software Process Improvement method park, Wetterkreuz 19a, 91058 Erlangen, Germany Tel. +49-9131-97206-316 mailto:[EMAIL PROTECTED] Fax. +49-9131-97206-200 http://www.methodpark.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
