19 Mar
2018
19 Mar
'18
11:16 a.m.
On Mon, Mar 19, 2018 at 11:11:11AM +0000, Owen Rudge wrote:
I wonder whether we really want a new thread / message. This should probably be moved to a thread pool api, but perhaps that can happen later on.
Mainly because on systems with a several network interfaces, this can result in the function call taking a long time, due to the delays enforced by the WSD/SOAP specifications. Sending messages simultaneously on several threads speeds this up considerably. On Windows the API appears to return near-instantly so I presume it's doing the same.
I realise it needs to be done in a background thread. I was commenting that creating a *new* thread for each message seems expensive, but this can probably wait for later.
Huw.