On 03/11/2014 22:22, Stephen Russell wrote:
...Start writing code in client server functionality. Now you no longer tie up resources like you use to.
+1 and preferably move to actually using client/server - meanwhile group your update logic and wrap each related set of updates in a transaction - with no logical opportunity for the user to 'leave' before it's complete (if in doubt set a very short timer on the transaction and rollback if it times out). That way there shouldn't be any significant resources tied up between updates.
_______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
