On 1/17/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
<snip>
>> About the command pattern applied to our services we are already working >> on a common infrastructure to reuse part of our network layer between >> services and prepare for asynchronous handling: you can look at the >> smtphandler in james 2.3 for the first implementation, you can look at >> the handlerapi-experiment for a more advanced solution we're working on >> as an experiment. > > the best plan would be to use SEDA > > this requires use of messaging APIs The architecture now in handlerapi-experiment supports SEDA (specifically it has been wrote with MINA in mind). And there is a command pattern.
what approach are you using to the scheduling architecture? master thread pool with mailboxes pushing tasks onto a queue? per mailbox thread pools? something more sophisticated? approach to the scheduling algorithms? are you using a library to manage the concurrency? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
