-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Friday, March 14, 2003 12:14:25 PM RE: "when a server is not a server..."
Greetings Thomas, On Thursday, March 13, 2003, 7:52:10 PM, you wrote: TF> Want to talk with me about semaphores and how file TF> locking works? Or what physically happens when a file on a network TF> drive is accessed for writing by two users at the same time and why TF> this *will* (not *could*) cause data corruption? It shouldn't. Once the file is locked it should, under proper programming, be locked to a write function. It should remain open to a read call but past that I cannot fathom a data corruption in this instance. If the programmer of the application properly coded the program and the first user opened the file to write function, and created the lock call, this would force the handle closed to write therefore causing user two no access. In some instances this could happen if the write calls were exactly simultaneous but that has a probability of about a million to one. Anyway ... - -- Regards, DG Raftery Sr. I haven't lost my mind; it's backed up on tape somewhere. The_Bat! 1.63 Beta/7 -----BEGIN PGP SIGNATURE----- Version: PGP for Business Security 6.0 Comment: http://home.nycap.rr.com/rafteryfamily/DG_Raftery_Sr..asc iQA/AwUBPnIQrzaPwvRMcz9cEQK2YgCdGiz9JZbCWoKhm01MWfWM2nNew80AnRas ALzfB65/2FwWYrK+3BtgDwOt =i4JA -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
