i found time over the last week or two to take a look at MINA and understand better the words it uses. i now suspect that we've been working towards similar architectures from different perspectives.
i broadly agree with Joachim (see https://issues.apache.org/jira/browse/JAMES-725): the first step towards being able to use SEDA for IMAP would be to refactor the IMAP commands into codecs, messages and processors (something like http://svn.apache.org/repos/asf/james/server/sandbox/design-doodles/imap/messaging-api/i2/step-one-sequence.png). but i'm most interested in adequate performance for my local james server. this means hacking a version with SEDA and scheduling as soon as possible. so, for me i need to do a big bang and port all commands so that they can be used in a new messaging architecture (rather than Joachim's gradual transition). i'd prefer to execute these changes which allows james to take maximum value from whatever code i produce but this is secondary (for me) to creating an IMAP implementation with adequate performance. opinions? what's the best approach code wise? how far is the new fetch implementation from being completed? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
