Fwd: Re: [dev] Re: [cvs] commit: horde/lib Registry.php

Chuck Hagenbuch chuck at horde.org
Fri Jan 23 07:45:11 PST 2004


I don't entirely follow...

----- Forwarded message from jan at horde.org -----
    Date: Fri, 23 Jan 2004 16:39:07 +0100
    From: Jan Schneider <jan at horde.org>
Reply-To: Jan Schneider <jan at horde.org>
 Subject: Re: [dev] Re: [cvs] commit: horde/lib Registry.php
      To: Chuck Hagenbuch <chuck at horde.org>

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>>> Log:
>>> looks like we meant to check READ perms here.
>>
>> Did we? I think the SHOW perm makes more sense because we not only prohibit
>> access to the app but also don't show it in the menu.
>
> Well, the comment and the debug message both said READ, and the perms go in
> order SHOW -> READ -> EDIT -> DELETE. SHOW is just a "you get to know it's
> there, but not what it is" kind of thing.

That makes sense. I guess it doesn't makes sense, ie is too much overheader,
to use both, SHOW and READ for the menu vs. application access then?

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - Neue Wege des Lernens
http://www.tip4all.de - Deine private Tippgemeinschaft



----- End forwarded message -----


-chuck

--
Charles Hagenbuch, <chuck at horde.org>
"Here, I brought some cole slaw. It's made from peeeooople! Just kidding."


More information about the dev mailing list