RE: [PEAR-DEV] LiveUser
| From: | Lukas Smith | Date: | Wed, 13 Nov 2002 11:00:32 +0000 |
| Subject: | RE: [PEAR-DEV] LiveUser | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-10754@lists.php.net to get a copy of this message | ||
> From: Markus Wolff [mailto:wolff@21st.de]
> Sent: Wednesday, November 13, 2002 11:48 AM
> To: smith@dybnet.de
> Cc: 'pear-dev'
> Subject: Re: [PEAR-DEV] LiveUser
>
> Am Wed, 13 Nov 2002 11:33:00 +0100 schrieb "Lukas Smith"
<smith@dybnet.de>:
>
> > what is still out there on our mission critical todo list?
>
> IMHO, that´s first and foremost a less complex perm container and
Docs,
> docs, docs :-)
I agree
> > I still have mapping of auth and perm containers on my list an
getting
> > the MDB backends to work again. I will also take a look at the
complex
> > container once more and ensure its working and tweaking it. I intent
to
> > do this within the next 7 days.
>
> What do mean by "mapping of auth and perm containers"?
>
Well I am talking about the issue of mapping ID's from an auth container
to an ID in the perm container. As discussed previously the goal is to
not have to require any modifications to the auth container.
The solution:
1) there is a table in the perm container with the following fields
(field names are not final at all yet):
auth_name | auth_id | perm_id
auth name:
will be an arbitrary name given to an auth container in the xml conf
file (or if none is given it will use the dsn or something like that)
auth_id:
this will be the id returned by the auth container
perm_id:
this will be the id used within the perm container
2) optionally the auth container can ask the perm container to generate
a new id. Then no mapping is required.
regards,
Lukas