When I think about.. maybe I'm thinking about this the wrong way again.. is what I'm talking about effectively just using asynchronous exchanges, since each exchange that is returned to my service unit asynchronously, it will be a different thread.
On Fri, Aug 14, 2009 at 12:57 PM, Ryan Moquin <[email protected]>wrote: > I had a quick question about handing exchanges asynchronously for long > running tasks. Let's say I had an exchange come in, that was requesting a > bunch of work to be done that could be parallelized (I think that's a > word). Would I take advantage of the threadpool in servicemix, from inside > my component? or would I want to use my own thread pool to keep from tying > up the servicemix thread pool? Would there be any portability implications > either way? > > Thanks for any input! > Ryan >
