The bulk service manager can be configured in various ways. Some of them (e.g. the HTTP file service) won't always be passed to the operations. This PR changes that.
Use case:
We are using NAT. Thus creating and closing HTTP connection to the same destination at a very fast pace leads to resource problems.
This MR allows using one HTTP file service for all operations of the service managers. Thus one could use one connection pool for all HTTP requests of these. This avoids creating and closing connections caused by many HTTP file service instances used for one HTTP request only like done before.
The bulk service manager can be configured in various ways. Some of them (e.g. the HTTP file service) won't always be passed to the operations. This PR changes that.
Use case:
We are using NAT. Thus creating and closing HTTP connection to the same destination at a very fast pace leads to resource problems.
This MR allows using one HTTP file service for all operations of the service managers. Thus one could use one connection pool for all HTTP requests of these. This avoids creating and closing connections caused by many HTTP file service instances used for one HTTP request only like done before.