Robert Burrell Donkin ha scritto: > On Nov 6, 2007 2:34 PM, Robert Burrell Donkin > <[EMAIL PROTECTED]> wrote: >> On Nov 6, 2007 1:26 PM, Zsombor <[EMAIL PROTECTED]> wrote: > > <snip> > >>> I think the subscription status should stored as a User attribute (as a >>> string list for example). As for IMAP we need several other user attribute >>> to store, I think it would be benefical, if we can extend JamesUser with two >>> method: Serializable getAttribute(String); and void setAttribute(String, >>> Serializable); In that way, we can store assigned shared namespace, acl, >>> quota objects, and so on. >> sounds good >> >> allowing meta-data to be stored with a user sounds generally useful. >> objects give flexibility but do have some disadvantages. > > opinions? > > - robert
A possible problem with this is that often the UsersRepository pluggability is used to authenticate users to a remote service. Often this service is readonly. The "attributes" you propose to add is instead some preference specifically related to a given protocol of JAMES. Maybe the right solution would be to split the UsersRepository in "AuthService" and "UserPreferenceService". IIRC we discussed this in past, but I don't remember anymore the result of the discussion. BTW I'm also fine with what you proposed. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
