[jcifs] setReadOnly, setReadWrite, or setAttributes?
Michael B Allen
mba2000 at ioplex.com
Wed Oct 29 17:30:40 EST 2003
>> > filesystem offers a completely different set of attributes, extended
>> > attributes, ACE's, etc. The protocol is tuned to provide support for
>> > FAT and NTFS semantics.
>> Huh? NTFS has these attributes. I don't know how they're implemented but
>> from the protocol view they're exactly the same.
>> Extended attributes will need some more thought but I'm not sure if I'm
>> ready to tackle them this time around :(
> Hmmm... Then NTFS offers a very large superset. EAs, by the way, are a
> throwback to OS/2's HPFS. I guess I was just thinking about the fact that
> the protocol is tuned to the specific OSes it was meant to support...
Oh, by extended attributes I thought you meant ACEs, ACLs, SIDs and all
that. So how do you get and set "extended attributes" and what are they
used for? Otherwise I don't think doing access control lists et al will be
useful unless we can do RPCs to make use of the SIDs. Ahtough we would be
able to copy them with copyTo ... mmmm.
A program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes the potential for it to be applied to tasks that are
conceptually similar and, more important, to tasks that have not
yet been conceived.
More information about the jcifs