On 2/7/2011 1:35 PM, Andrew Deason wrote: > > I'm just saying, if the not-recommended s:anyuser case sometimes breaks > as a result of this, it is not intrinsic. We can modify the client to > make it work.
In the dropbox case the client has no need to read anything from the server. It should only be creating new files. Restricting the writing to only dirty data doesn't matter. It certainly would make the client faster. The Windows CM already only writes the dirty portions of a 1K page. If the Unix CM is reading beyond the end of file as part of preparing a chunk to be written, that sounds like a bug to me. The Windows CM never reads data from the file server beyond the known EOF. If the file is new, the file length is 0 and the client prepares the page locally without file server interaction. >> This problem is not new and has been well-known in the AFS community >> for quite some time. The "What are dropboxes?" section (2.22) of the >> AFS FAQ: Using AFS page includes the following: > > The general problem, yes. But the text you are referencing treats it as > a security/visibility problem. The change Derrick is talking about > introduces a new problem where the write to the dropbox file could > potentially fail, making the mechanism effectively break depending on > the use case. > > I'm not saying that's necessarily a big problem, but it is a new thing > that users should be made aware of. The write will never fail. >> I think it would also be worth-while to have a file server option that >> disables "i" for anonymous in its entirety. > > Such as gerrit 217? >
signature.asc
Description: OpenPGP digital signature
