Danny,
[please note: I'm posting the reply on james-dev@]
I'm beginning to think that we need to organize the James v3 discussion, and
focus on one thing at a time until we have a consensus on the design. Then
we can put them design notes into the status file, and people can pick
things to work on confident that there is a consensus on the overall
approach.
Now ... with respect to Mail and User attributes, Serge has indicated that
he'd like to be able to store serialized objects. I have some reasons for
agreeing with him, such as being able to store proxy objects in the store.
I agree that they impact store design. Stores are one of the things that I
think really need to be reconsidered from multiple perspectives.
--- Noel
-----Original Message-----
From: Danny Angus [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 09, 2003 10:53
To: James Users List
Subject: Mailet Mail attributes
Serge wrote stuff including:
> class loading. Beyond that, I see mailet attributes, mordred
> preplacement, and I'd like to explain my virtual mounting ideas,
I've been wondering about Mail attributes, and how they would impact
repositories.
I thought that we should limit attributes to being Strings, is there any
_real_ need to do more?
d.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
