-James
Andrey Shulinsky wrote:
Hi, Warwick, James, everybody!
My 2 cents about the matter.
Warwick Burrows wrote:
Many authorization implementations have the concept of a "traverse"
permission as I outlined in an earlier email. A permission
that allows the
user to "traverse" into a particular directory but not read
the files
in that directory. They must have traverse permission on the parent
directories
too of course. The read permission in Slide is handling both the traverse and read permission cases right now. By adding a
"traverse"
permission it would allow these guys to control who can
read the docs
in parent directories but not stop others from traversing down to directories that they can read.
Just to clarify, your "traverse" permission *is* how the read permission works on collections. If you get a list of the children of a collection you will only see the children to which you have read access as well.
It depends on the client, actually. WebFolders are OK, but IE, for example,
shows all children - with 2.0, at least.
Yours sincerely, Andrey.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
