Am Freitag, den 28.04.2006, 21:18 -0400 schrieb Noel J. Bergman: > Stefano Bagnara wrote: > > > All the configurations/components introduced in 2.3.0a1 needs to be > > reviewed and possibly renamed/moved/changed. > > That's fair. > > > I would like to also change the smtp command handler code before a final > > release, otherwise we will have to mantain 2 totally different fastfail > > codes. > > I disagree. We document this as INTERNAL ONLY, we do NOT encourage people > to write new ones, and warn them that the API will change, we get the > product shipping, and THEN we clean up the API. Unless there is something > in the current API that blocks OUR ability to ship a release. >
Thats also a good point. But a "better and more pluggable" smtp handler code whould be also a very nice think. It whould be more pluggable at all and when adding new features the core solid code will not affected. So also the testing and fixing bug will be maybe a bit easier cause if the bug only happen on the new "pluggin" you know were to search and can also exlude only this and notify the developer of this code . > When we provide the API for external use, we will also want to add a loader > so that people can register handler packages. > > > I would also like to introduce the command handler pattern to pop3 and > > remotemanager: this would add a great level of extensibility to James. > > Same as above. I agree with wanting to add functionality, but we first need > to consolidate what we have, and get a solid release out, and THEN add > features. > If we want to not any new featues or improvements yet we should write a new roadmap for next changes and whats the main goals. bye Norman
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
