>> As long as anyone else using those files in their code uses exactly >> the same name, it will work. >> > Thanks James. > And I suppose, when running on a shared server, it doesnt hurt to reduce > the likelyhood of a conflict by using a more unique name like > FileChange3076 instead of FileChange
An easy way to ensure a unique name for such a kind of locks is to use the file's full path name as lock's name. That's the way I implemented it on this CFC: http://www.olimpo.ch/tmt/cfc/tmt_file_io/ ---------------------------- Massimo Foti, web-programmer for hire Tools for ColdFusion and Dreamweaver developers: http://www.massimocorner.com ---------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:263503 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
