"Paul Volpato" <[EMAIL PROTECTED]> writes:

> I certainly hope this isn't where TurboGears is going - when it does
> that why not just call itself Zope3 2?  If this is the eventual plan,
> I would say make it entirely optional - and certainly don't make it
> xml.  If people wanted to play with config files they'd do java web
> development :)

Unfortunately, as of today, if you want to let your clients free to define
permissions and access restrictions you have to edit the code (or let them do
it). 

I prefer users editing config files (for which I can easily make a web
interface...) rather than code.

> It seems like a useful use case at first glance - but do you really
> want someone who doesn't understand how the system works setting the
> security on it?

Sometimes yes.  Specially when you group functionalities and they are your
client's business, not yours.  Imagine that you deployed your application and
two years later your client says: "Now we have a new management function on
the company that needs full access to finance data, no access to technical
data, etc.".  Why wasn't he able to define that by saying something like:

[finance]
read = ..., new_group
write = ..., new_group
delete = ..., new_group
update = ..., new_group

?  Easier than you having to go there (where is "there"?  in the other office?
another city? another country?) to do that.  After all, after two years you'll
want to take a look at your client and see how the system is solving their
problems, what else you can sell them, etc.

> I think that the security should really be done by the developer.  The
> idea that an admin can sit down in front of a foreign system and start
> reassigning permissions is not realistic.

It happens on several CMSs and several ERPs.  I believe it works.

-- 
Jorge Godoy      <[EMAIL PROTECTED]>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to