[Zope-DB] Per-user connections

[Iain Anderson]

Am I missing the bl***ing obvious here :-) ... but why can't you use 
whatever is your normal Zope authentication and then pass 
AUTHENTICATED_USER into your ZSQL methods for authorisation, auditing etc.

Oracle now recognises the difficulty of registering every possible user in 
the database and e.g with the use of virtual private databases expects to 
pick up user/authentication information from the context of each database 
call.

--On Monday, December 09, 2002 11:17:46 +0100 Yves Bastide 
<Yves.Bastide@irisa.fr> wrote:

> M.-A. Lemburg wrote:
>> Just to understand this discussion: why are per-user connections
>> needed ?
>>
>> Is it because you want to manage authentication for these
>> connections on a per-user basis ?
>>
>
> Yes (authentication, authorisation, auditing)
>
>>  From a technical point of view, it should be possible to
>> place a Zope connection object into a user or even session
>> object, since they are pickleable. Even transactions should
>> work, since each .query() call registers itself with the
>> TM.
>>
>> The only point to watch out for is thread safety, since probably
>> not all DAs provide thread locks around the various method
>> calls.
>>
>
>
>
> _______________________________________________
> Zope-DB mailing list
> Zope-DB@zope.org
> http://lists.zope.org/mailman/listinfo/zope-db
>



Iain (Jethro) Anderson - DBA (ISYS) University of Bristol
Pigsty Morris   City Clickers Step and Clog
Instep Research Team  Insword Rapper

"Never give a sword to a man who can't dance"