Hi Steve,
I am not sure that a polling is a good solution.
Here are some additional details:
The server indeed keeps the getValue call blocking for a given delay (configurable). After this delay the call returns. (The client calls timeout is also set to a configurable delay. But indeed no timeout will occur.) But other operations (control for example) might also take some time to proceed. The problem is that the client application has
to exit at some time. Therefore, the client require
a way to stop the ongoing operation calls in order
to exit smoothly (as fast as possible).
Finally, time consuming control operations for example could not be implemented through pooling...
Nevertheless, the problem of repeated "instant" polling is that it will generate useless network traffic + consume resources just to know that there is nothing to get...
true. but if you use keepalives on the TCP link you generate useless traffic; if you dont your client wont ever know that the server at the far end has ceased to exist.
The purpose of this application is to be efficient
at runtime, without using complex mechanisms (architecture) to allow a simple client application stop.
Thus, is there a way to stop an operation call at Axis level ?
Not yet :)
