Hello,
ZEO already supports authenticated logins. Based on the login I'd like
people to be able to access some objects and deny access to others.
First I thought I'd do the access restrictions on the application level.
This doesn't seem to be too easy though, because a user might have access
Am 22.05.2010, 14:17 Uhr, schrieb Nitro ni...@dr-code.org:
Each object and each user would have
something like a permission_id attribute.
Could also be a mapping oid - permission id.
-Matthias
___
For more information about ZODB, see the ZODB Wiki:
On Sat, May 22, 2010 at 2:17 PM, Nitro ni...@dr-code.org wrote:
ZEO already supports authenticated logins. Based on the login I'd like
people to be able to access some objects and deny access to others.
First I thought I'd do the access restrictions on the application level.
That's the only
Hi.
Following up on my idea of using pickle protocol 2. I implemented this
in a fully configurable fashion on a branch, mainly to ease
benchmarking and testing of the different variants.
My conclusions (maybe for future reference):
- There's no significant win of just switching the pickle
