>�From: Charles Benett <[EMAIL PROTECTED]>
>�Date: Tue Aug 29 13:13:57 EDT 2000
>
> But shouldn't james.usermanager.UsersRepository be an interface? With,
> for example, a UsersFSRepository and a UsersLDAPRepository?
> UserManager has a method 'public UsersRepository
> getUserRepository(String name)', which, I think requires making
> UsersRepository an interface, before writing an LDAP implementation?
> If that is correct, I'm happy to split the current UsersRepository into
> an interface and an implementation. If that's wrong, please advise.
>
> Charles
I think you're correct that you need an interface and an implementation. In fact, I
was debating with myself last night on how much tie-in to mail accounts the mailet API
should have. Is UserRepository an interface within Avalon/James or within the mailet
API? At first glace it seems there shouldn't be any tie in, but at the same time it's
useful to have the MailetContext (the mailet container, i.e., the mail server) to
support delivering the message locally and seeing if someone is a valid user. But I
finally decided the UserRepository (as a class or now an interface) should be within
Avalon/James. Anyway, Federico might have comments on this as well. (sorry for the
tangent)
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
