Re: [DISCUSS] Improvements on client function execution API

[Jacob Barrett]

> On Aug 22, 2019, at 11:55 AM, Jacob Barrett <jbarr...@pivotal.io> wrote:
>> On Aug 22, 2019, at 11:29 AM, Dan Smith <dsm...@pivotal.io> wrote:
>> I took a look at the C++ API. The C++ API also has a
>> ResultCollector.getResult(timeout) method. Does that timeout do anything,
>> given that execute(timeout) already waited for the given timeout?
> 
> The C++ client will wait on getResult until all the results have arrived or 
> timeout has expired. If timeout has expired an exception is thrown. It does 
> not try to cleanup the connection or threads processing the responses from 
> the server. Those connections should either eventually get data and fill in a 
> now abandoned ResultsCollector or timeout based on the execute timeout and 
> close the socket.

Scratch that… On further investigation the execute is blocking, but can timeout 
when timeout expires. The getResult timeout appears to really be pointless. 

-Jake