On 2/8/06, Jason Huggins <[EMAIL PROTECTED]> wrote:
>
> Luke Skibinski Holt wrote:
> > there is no per-record permission system
> > for users yet (or ever...). However this seems an unlikely scenario and
> > more often as not you will only want your users only looking/updating
> > data they have c
Just a quick note from someone with a lot of Zope experience finding
the world of Django very very interesting...
In Zope, there is a *lot* of flexibility in terms of
authentication/authorization. I couldn't say whether it is full ACL or
not, but it certainly seemed it to me.
However, we rarely
Hi Jason.
Your scenario only covers a very basic scenario, where 1 user can do
anything to a particular record.
It kind of falls down when you need to assign rights to actions.
ie..group/user X can add a new invoice, but only 'group/user Y' can
modify an existing invoice.
So while a constrained
Luke Skibinski Holt wrote:
> there is no per-record permission system
> for users yet (or ever...). However this seems an unlikely scenario and
> more often as not you will only want your users only looking/updating
> data they have created.
I had an "aha!" moment on this topic last night. My rep
Depends on your requirements and how much you can trust your users. If
you're talking thousands of users, each user will be stored as a record
in the database, and each of the databases supported by Django can
easily support millions of records (performance dependent on
hardware/design of course).
Not clear here on the authentication system. Is itdesigned for back-end
users or is it more generalized any authentication usage. Can it
handle thousands of users accounts?
6 matches
Mail list logo
