> this general idea has worked well for me-
> (a) hierarchical namespace and
> (b) Name-Value attributes per node.
> One of the attributes of a node could be InputStream
> or MimeMessages.
The problem with that approach is that it presumes a homongeneous storage
format. Even using JNDI SPI, you don't want to try supporting mbox or
maildir format that way. Plus the JavaMail interface provides more domain
specific support that we want.
> JNDI like repositories may be a bit slower. There is need for a map lookup
The JNDI data model is nice and flexible, being basically a linkable
hierarchy of tuples. But computers aren't infinitely fast. I believe that
we can use JNDI for its primary design point, and not try to leverage it as
a uniform address space for all data.
> Very little need to evlove API or add other specific APIs for say Address
> Book, IM, Calendar etc.
If users are stored in JNDI, then I agree that user related content can be
stored there, too. If not the content, itself, then objects providing
access to that content.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
