On Tue, Aug 5, 2008 at 22:06, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > most people know that a long standing goal of mine has been to create > independent lightweight protocol components (eg no avalon) that are > used by JAMES but can also be used by other application.
+1, this general direction has my full support! Moving protocol related stuff into server-independent components will soon raise technical questions: 1. What _is_ the 'protocol' domain? 2. How does this domain interface with the rest of the system it is deployed in? 'Protocol' for me connotes closely with 'connection', 'paser', 'command' and 'command handling', and not so closely with 'session', 'session state' and 'interfacing backend services'. At some point we'd have to draw a line and define what's inside the protocol domain and how this interfaces with the rest. I tried to do this in a layered way (onion) in Vysper, not sure how much the architectural patterns from there can be applied to James. Another interesting aspect for me is that POP3 is somehow a functional subset of IMAP. How do we do this right without duplication? I am looking forward to disussing this in dedicated threads as it becomes neccessary. Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
