> point me, if you can....the right direction seeks me ;) > > where to start? i understand to a point, but the nuts > and bolts of it would be more effective to understand.
Unfortunately, I'm not going to be much help here. A lot of this stuff is part of a typical CS curriculum, so CS texts may be useful in this regard. You might google for "concurrency" or "dining philosopers" (a common concurrency problem in CS courses) and see what you find. Basically, in web applications, you have to consider concurrency issues all the time. For example, let's say you build a data entry interface that allows a user to insert, update and delete records. What happens if two people choose to update the same record at the same time? Typically, in most web applications I've seen, whoever pushes the submit button last will overwrite the changes made by the previous person. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
