Re: [infinispan-dev] Threadpools in a large cluster

No, I think it'll apply to all messages. A simple implementation could dispatch OOB messages to the thread pool, as they don't need to be ordered. Regular messages could be added to a queue where they are processed sequentially by a *single* thread. Pedro does implement ordering based on transactions (see his prev email), and I think there are some other good use cases for regular messages. I think one thing that could be done for regular messages is to implement something like SCOPE (remember ?) for async RPCs: updates to different web sessions could be processed concurrently, only updates to the *same* session would have to be ordered. Yeah, I agree implementing the regular message ordering ourselves would give us a little more room for optimizations. But it would make our part more complicated, too. Well, not for Total Ordering, because Pedro already implemented it, but for our regular async scenarios we'd need to add a thread pool (we want to allow 2 threads from different sources to access different keys at the same time).