while I'm on the subject of TODO's for the *next* release my de-avalon-ising of the existing transport mailets highlighted an artificial and needless difference in handling between User repositories (provided by a central User store) and mail repositories wich are all accessed directly by specification.
I think we should probably stndardise on one approach, either a repository manager for each, and repositories referenced by name, or refer to user repositories directly by specification. d. > -----Original Message----- > From: Danny Angus [mailto:[EMAIL PROTECTED]] > Sent: 26 September 2002 22:32 > To: James Developers List > Subject: RE: Aliasing > > > I tend to agree, its a fine grained distinction that would need to be > clearly explained. > Perhaps we should update the TODO with some of the stuff we're badying > about, > > this > remove Mailet hidden avalon dependancy > service/component > > What else? > > > -----Original Message----- > > From: Peter M. Goldstein [mailto:[EMAIL PROTECTED]] > > Sent: 26 September 2002 21:51 > > To: 'James Developers List' > > Subject: RE: Aliasing > > > > > > > > Noel, > > > > > I wouldn't change this right now, other than to clarify the > > documentation. > > > The user repository can be (and should be) revisited post-2.1 release. > > > > Ok. We'll leave it for now and revisit after 2.1 release. > > > > --Peter > > > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
