Next step for facilities in my mind are things like JMS servers, FTP servers, and SMTP servers. All of these are high on my priority list, as I'm going to need all of these facilities to address requirements of current and future applications built on Avalon technology.
In fact, let me further state that in the same way the merlin assembler distinguishes *servlet* components as specialized component, I would further propose that this same facility be extended to recognize the work that Aaron Farr has done in regard to Message Driven Services. IOW, a *special* component recognized in the merlin facilities that denotes that this component will *handle* a receipt of a JMS message via queue or subscription in the same way (conceptually) that the servlet component *handles* the receipt of an HTTP message.
Bottom-line is that we have these *transport* level facilities that need to be supported, but equally we need a framework for easily attaching handlers (components) to do something with the messages that arrive over the various transports.
I also forgot to add web services to the facility list above.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
