Noel, Serge, > [please note: I'm posting the reply on james-dev@]
yes sorry, absentmindedness seems to be my calling card these days. > 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. Quite agree, the changes I've made have deliberately been restricted to scratching one particulr itch, that it was difficult to develop and deploy mailets in isolation from james build process. Now that I've got it out of my system I feel no compunction to go mad, particularly not when I feel ambivalent about most of the other issues. I've raised a number of points recently simply in order to provoke the discussions we need to have in order to get a concensus. > 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. Fine by me. > I agree that they impact store design. Stores are one of the > things that I > think really need to be reconsidered from multiple perspectives. +1, but we don't have to do everything at once. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
