the work i've been doing on the branch is pure refactoring: moving around code that already exists. my aim is to factor the existing code base so that it's possible to experiment with SEDA based strategies including MINA without rewriting the protocol management logic. my plan is to approach this in an incremental fashion. this has the advantage that the code should be functional at all times. the disadvantage is that it's not as clear how the changes achieve the goal.
rather than waiting for a big bang merger, i'd prefer to move the changes in incrementally a week or two behind the current branch. so, i plan to cut a number of milestones so that developers can more easily understand what's going on and review a reasonable quantity of changes. opinions? i've been running http://svn.apache.org/repos/asf/james/server/sandbox/tags/seda-imap_M1 for a week now. seems ok. i'd like to merge these changes in sometime in the next couple of weeks. so if anyone who's interested could take a look this week that'd be great. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
