Hi all,
Consider this problem - we have a set of services outside of our control
(a mixture of doc/lit and rpc, that's not important though) which are
being orchestrated into a dataflow style workflow. At present we must
allocate one thread to each service invocation and this is potentially a
problem for cases where either a single workflow launches thousands of
services concurrently or where the workflow service itself is hosting a
large number of active workflows.
In principle it would seem possible to have a thread which was aware of
all currently pending SOAP operations (where the request message had
been sent but no response received) and which could poll some incoming
queue regularly, launching any neccessary threads if messages are present.
This implies a client manager component, I'm not aware of anything
analogous to this in the current architecture though?
Questions :
1) Is this covered in the Axis2 design in any way?
2) Is anyone else interested?
Cheers,
Tom
