Federico Barbieri wrote:
>
> Federico Barbieri wrote:
> >
> > Peter Donald wrote:
> > >
> > > >I'm keen to move JAMES to the new Avalon as soon as practical. My only
> > > >hesitation is: how stable is new Avalon and how long will porting take?
> > > >It may make more sense for a release of JAMES1.2, principally Serge's
> > > >new mailet api, which I think is pretty close, then transfer to new
> > > >Avalon.
> > > >Thoughts?
> > >
> > > Stability wise (as in performance) it is fairly stable. A lot more stable
> > > than past versions. It does a lot more error checking - thou a badly
> > > written thread can still screw it it should be much more safer. FWIW my
> > > mailserver ran for about 810 hours without fault before I pulled it down.
> > >
> > > If you mean stability as in interface wise then it is mostly stable (except
> > > for Manageable interface). Thou it may be better to release 1.2 as is and
> > > then upgrade over a few weeks and release again (better publicity) ;)
> > >
> >
> > Ups... I'll fix Manageable asap (now).
> >
>
> done.
>
> I've added build.bat and sh to james to make build similar to avalon
> (wich is great).
> Updated xerces. Now as for avalon you don't need anything but the
> javac.jar in your classpath for build.
>
After a few more time I think you're right... it's too soon to move
james basically becouse James needs the Selector pattern defined and
implemented.
So I'll work on it asap while james can move for example to log.jar (get
rid of Omero) to ease the move.
Opinions?
Federico
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
