Marco,
Your question doesn't entirely make sense. If we used JNDI, that would be
the interface to user repositories. The actual implementation is handled by
a service provider. One option would be to adopt ldapd, which provides both
an implementation and a JNDI service provider.
I don't believe that we would continue to use the existing user
repositories, other than to migrate them forward.
--- Noel
-----Original Message-----
From: Marco Tedone [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 27, 2003 18:10
To: James Developers List
Subject: Re: Storing quota info using JNDI
Users can be stored in the database as well as in folders, am I right?
Marco
----- Original Message -----
From: "Noel J. Bergman" <[EMAIL PROTECTED]>
To: "James Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, May 27, 2003 10:28 PM
Subject: RE: Storing quota info using JNDI
> Marco,
>
> The idea is simply that the user's quota would be stored as an attribute
> in the user record.
>
> --- Noel
>
> -----Original Message-----
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Sunday, May 18, 2003 16:50
> To: James-Developer
> Subject: Storing quota info using JNDI
>
>
> Noel,
>
> in the previous days you introduced some possibilities to specify a
> per-user quota service using JNDI. As I don't know a lot about JNDI,
> today I bought a book. Could you address me on the right topics to
> address this issue?
>
> Which is your idea to realize a per-user quota service?
>
> Marco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
