> > One of my notes points to a JMS (ActiveMQ) based spoolmanager. > > Yes, I've looked at ActiveMQ, ActiveCluster and ActiveSpaces. > But I don't think that this change is a simple drop-in, and > I would be concerned about performance and reliability. Not > that the code is bad, but the integration seems riskier for a > short term change.
I could agree on this. > It also seems orthogonal to a change that > uses one thread blocking for the event, and the rest are workers. I don't agree on this: probably in the JMS environment we would prefer that each worker (consumer) do its own work without the need of a single consumer that dispatch the messages (e.g: consumers could be installed in different machines) Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
