yep, I think we have established that :-p LOL
-----Original Message----- From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]] Sent: 16 October 2002 16:33 To: CF-Talk Subject: RE: 'Locking' a process Problem with a named lock is it's only available for the short time that a single cfmodule is accessing that file -- I _think_ he's talking about something more like a source-control check-in/check-out idea. > Wrap it with a named lock ? > HTH > -----Original Message----- > From: Robertson-Ravo, Neil (REC) > [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 16, 2002 15:16 > To: CF-Talk > Subject: 'Locking' a process > Anyone got any ideas on how to do a pseudo lock on a process within an > application? > My example is that I am reading from an .xml file whose contents can be > edited and then updated. I want to be able to lock this process so no > other user can overwrite the data while another user is performing the > action on it (or at least flag the fact that its open by another > process.) . > Neil > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
