Dear Wiki user, You have subscribed to a wiki page or wiki category on "James Wiki" for change notification.
The following page has been changed by SergeyLubinskiy: http://wiki.apache.org/james/SummerOfCode2005/SergeyLubinskiyFastFail ------------------------------------------------------------------------------ * DIY container plumbing pico-container style (shouldn't be too much code) closely along the lines of the current [http://james.apache.org/javadocs/org/apache/james/transport/JamesSpoolManager.html JamesSpoolManager] implementation === Advantages for ASF === - * A solid foundation for implementing a feature heavily demanded by current internet realities - SMTP fast fail + * A solid foundation for implementing a feature heavily demanded by current internet realities - SMTP fast fail - * Possible a new insight on the issue of reconfiguring components inside IoC containers + * Possible a new insight on the issue of reconfiguring components inside IoC containers === Deliverables === Totally revamped drop-in replacement for the existing [http://james.apache.org/javadocs/org/apache/james/smtpserver/SMTPServer.html SMTPServer]. Possibly patches or pieces of coded targeted for ASF containers. === Schedule === - * start active coding around June the 22nd, the expected end of examination session + * start active coding around June the 22nd, the expected end of examination session - * deliver version 0.1 by July the 12th, this version should prove that configuration and more importantly reconfiguration of "protocolLets" along the path: "inspect class via reflection - build JMX type descriptor - configure via JMX - save to XML" is feasible and desirable + * deliver version 0.1 by July the 12th, this version should prove that configuration and more importantly reconfiguration of "protocolLets" along the path: "inspect class via reflection - build JMX type descriptor - configure via JMX - save to XML" is feasible and desirable - * deliver version 0.2 by July 25 - "protocolLets" actually able to see other blocks visible to SMTP server (they get them via setter methods), the new SMTP block actually able to accept main and feed it into the existing processor pipeline + * deliver version 0.2 by July 25 - "protocolLets" actually able to see other blocks visible to SMTP server (they get them via setter methods), the new SMTP block actually able to accept main and feed it into the existing processor pipeline - * deliver version 0.5 by August 14 - some protocolLets actually make sense and do some useful Spam blocking + * deliver version 0.5 by August 14 - some protocolLets actually make sense and do some useful Spam blocking After August 14 fix react to bug reports and requests for enhancements. If time permits look into integration with scripting languages.
