You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2003/05/01 00:00:33 UTC

RE: Repositories (Design suggestion)

> I'm thinking towards iCalendar/iCAP, vCards etc, or even SIEVE scripts.

The kind of thing that you're talking about would probably be stored in
JNDI, not in JavaMail.  A user's groupware data would be associated with his
JNDI user entry.  Likewise, there is a bullet item in the Wiki regarding
"User-specific Pipeline".  One simple thing could be a Sieve package that
ran SIEVE scripts associated from a user's record.

> Allowing a store to store arbitrary items would give service
> implementers a better way to reuse the store components for
> their needs.

Why do you think I am pushing JNDI?  JNDI provides federated, hierarchical,
named, searchable storage of named entities and their named attributes.
Where JNDI is not the optimal access mechanism, the most likely solution
will be a JDBC connection, which could be acquired via JNDI.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org