This sounds like there is room for optimization, right? Why not always
allow read access to data that is never returned to the outside? Peter,
is it this you wanted to indicate?
Oliver
[EMAIL PROTECTED] wrote:
Jun,
currently it's a *must* in Slide. The Slide "helpers" (which build-up
the Slide engine) internally need read access to all upstream folders to
check permissions and locking, or resolve bindings. As currently the
"helpers" cannot distinguish internal from original calls, they check
the preconditions on each call.
Regards,
Peter
-----Original Message-----
From: Hu Yong [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 11. August 2004 12:04
To: Slide-user-forum
Subject: Why need read privilege on upstream folders to
achieve a write permission
Hi everybody,
I've a problem about Slide ACL. What we want is very simple:
We have a document tree managed by slide. We want to assign
write priviliges on some nodes(folders) to specific users.
However, we found the users with assigned write privileges
still cannot write on those nodes until we assign the users
read privileges on all upstream folders.
For example, the document tree is like this:
A1
- B1
- B2
- C1
- D1
- C2
- B3
We want to assign user Don write privilege on D1. However, we
found although the write privilege is granted successfully,
Don still can't write in D1 (like create a subfolder). But if
we assign Don read privilege on C1, B2 and A1, then he can
write in D1.
I'd like to know whether this is a must in Slide or we can
change some configuration to skip assigning read privilege on
the upstream folders. Thanks.
regards,
Jun
---------------------------------------------------------------------
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]
