Open simongregorebner opened 9 years ago
From my point of view this default timeout need to be set-able via the context properties. I guess 2 timeouts might be useful, one for creating the channels and one for the operations on the channels I would suggest something like: CA_CHANNEL_TIMEOUT and CA_CHANNEL_OP_TIMEOUT
Status Update
Up until now this has not been implemented so the issue is still relevant. The current workaround is to use the asynchronous functions with constructs like the following:
channel.getAsync().get( timeout, timeUnit );
channel.putAsync( value ).get( timeout, timeUnit );
For synchronous functions like get(), put(), connect() there should probably a default timeout instead of blocking forever. This timeout should be configureable via context properties, I guess ...