> 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. -Jake
- [DISCUSS] Improvements on client function execution API Alberto Gomez
- Re: [DISCUSS] Improvements on client function execu... Anilkumar Gingade
- Re: [DISCUSS] Improvements on client function e... Alberto Gomez
- Fwd: [DISCUSS] Improvements on client function ... Dan Smith
- Re: [DISCUSS] Improvements on client functi... Jacob Barrett
- Re: [DISCUSS] Improvements on client fu... Jacob Barrett
- Re: Fwd: [DISCUSS] Improvements on client f... Alberto Gomez
- Re: [DISCUSS] Improvements on client function execu... Jacob Barrett
- Re: [DISCUSS] Improvements on client function e... Alberto Gomez
- Re: [DISCUSS] Improvements on client functi... Dan Smith
- Re: [DISCUSS] Improvements on client fu... Alberto Gomez
- Re: [DISCUSS] Improvements on clie... Alberto Gomez
- Re: [DISCUSS] Improvements on ... Alberto Gomez
- Re: [DISCUSS] Improvements... Dan Smith
- Re: [DISCUSS] Improvements... Jacob Barrett