David Bear wrote: > This is way to difficult. I wonder if there might be a better way. > > Since afs for windows uses a local smbserver, I wonder if that might > be hacked somehow to write temporary files to the local disk at the > same time that it passes the data off to the cach manager. It could > keep a files in a queue and push out the old like a LIFO queue...
Assuming all you were doing is copying a file into AFS that might make sense. But this is not how AFS is used in general. Windows applications work with byte ranges not whole streams. Everytime the cache manager touches a file in AFS it would have to copy the file down to this offline cache. In other words, what you want is Microsoft's Offline Folders. With Offline Folders, you read and write files from local disk and periodically synchronize the contents of the local cache with the remote file system. AFS does not have this functionality nor do I believe it should. I support the idea of devoting the necessary resources to implement disconnect mode in the Windows AFS client. If there was a network problem in this case, the data would remain in the client until such time as the data could be written successfully to the server (provided that there was no conflicts with write from other clients.) Doing this work is on my road map. However, there are no resources currently available to do it. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
