|
|
When calling a service via WS-Stack / Listener for XML/SOAP to a Broker, each service call results in 3 calls to the Broker.
Logon
The service call it self
Logoff
This is the case even if AUTOLOGON is ON.
A. I would be possible to avoid the LOGON call, with AUTOLOGON=ON, the needed credentials could be sent with the service call.
B. And either the LOGOFF could be avoided completely or at least the answer could be sent to the service call, before calling the broker again with the LOGOFF.
And B. could implemented alone.
The reason this comes up now is:
We have now moved part of our EntireX servers into the cloud and that means that the physical distance between the servers and the broker has grown significatly, so the latency has gone up from below 1ms to about 30 ms, with 3 calls we have added almost 100ms to each call, which means that we cannot move our PROD servers into the cloud.
| Use Case | We have now moved part of our EntireX servers into the cloud and that means that the physical distance between the servers and the broker has grown significatly, so the latency has gone up from below 1ms to about 30 ms, with 3 calls we have added almost 100ms to each call, which means that we cannot move our PROD servers into the cloud. |
We will enhance the Broker attribute file, add new attribute on service level to do logon-send-logoff in a single send call and introduce a parameter in XML-client to avoid for such a service definition the logon() and logoff() calls.
We are scheduling this for the next release - OCT24.