<[EMAIL PROTECTED]> writes: >> As I mentioned in an earlier post -- the solution is to ensure that >> metakit files on network shares are opened for exclusive access. You >> can write your own c4_FileStrategy implementation to handle this and >> use it in the c4_Storage constructor. The PathIsNetworkPath Win32 API >> is also a useful function here. > >No, you can't prevent an antivirus from scanning your file. Just >looking at the file attributes is enough to corrupt it (if it's >followed by another commit). At least, it is what I observe with my >program. If you too have an application that can commit to a metakit >file through a network, please make the test and tell me if you >observe the same corruption. Maybe it's my program's fault, but >sincerely I doubt it.
I can't post you the whole lot but I can give you the re-implementation of c4_FileStrategy that we use. We have some 32GB of data in over 18000 files on a Windows network shared storage and none of them are corrupt and people do use them over the network share. -- Pat Thoyts http://www.patthoyts.tk/ PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD _____________________________________________ Metakit mailing list - Metakit@equi4.com http://www.equi4.com/mailman/listinfo/metakit
