2014/1/3 Bertrand Delacretaz <bdelacre...@apache.org> > Hi, > > On Fri, Jan 3, 2014 at 2:12 PM, Carsten Ziegeler <cziege...@apache.org> > wrote: > > ...I'm not so sure about timeouts by the caller - I would assume that the > > configured timeout for the executor is a sensible value. If you want to > > specify something else for a specific client, this client would need to > > know which HCs it's executing, how long it takes etc.... > > Yes, my use case is executing the HCs tagged with "external" for > example, I know those take longer than the performance counters for > example, so I set a longer timeout for their execution to have a > better chance of having fresh results. > > > ...We have discussed other things like forcing a HC to run (and not to > use the > > cached value), I'm not sure about those either.... > > This is less clear for me as well. > > > ...We could think about adding an Options argument to the execute method > where > > we add getter/setters for these things.... > > Yes, we can add a second execute method later that takes options. > > Ok, if we already know about some options we could add this already now. Or we gather first some more expierence and add it later :)
> > > > ...But I think we need a clear result if the timeout is reached to allow > > clients to correctly display this and retry at a later point of time.... > > As is you can compute the age of a result, that should already help. > Hmm and what about the case, where there is no result yet and the HC takes longer than the timeout? Carsten > -Bertrand > -- Carsten Ziegeler cziege...@apache.org
