>>1. Lock the file (noted on the server) >>2. Download the HEAD revision - the latest copy of the code - in case >>someone else has changed it since their last download >>3. Start working on their job
>>Then once they are finished with their files, they commit them. This >>does two things... >>1. Releases the lock on the server >>2. Makes the file read-only on their working copy again This is almost how I imagined it. The only thing, do they have to look by themselves for the new things to update, or is this automatically done during some login procedure ? -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:265173 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
