Venkataraman, Narendra wrote:
Regarding moving message handler code to DATACmdHandler code would make the architecture inflexible, if somebody wants to develop their own Custom Datahandler and still reuse some of the message handlers.
Well, now you can overwrite the DataCmdHandler with a DataCmdHandler that is not compatible with the current DataCmdHandler and break that onMessage stuff. In fact we have SMTPHandler code that work only if the DataCmdHandler do something specific (set a message in the session).
This seems like a "weak" contract and I like much more to remove that dependency by moving the MessageHandler handling to the DataCmdHandler. MessageHandler is IMHO a further layer build on top of the "low level" protocol handler chain.
If we move that to the default DataCmdHandler then you can extends the default DataCmdHandler if you want to keep the MessageHandler/onMessage support, or write your own custom handler with no support of MessageHandlers, as you prefer.
Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
