Re: Good guy timers
David Barbour <[email protected]>
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <CAAOQMSvcZ_VzoSyQweJMBExaGCf+AJN8m=pBo87E-UfJ3bASYw@mail.gmail.com> |
On Mon, Mar 31, 2014 at 12:22 PM, Jed Donnelley <capability-iCFHVraI1K1Wk0Htik3J/[email protected]>wrote: > I of course bristle a bit at the adverb "just" in the above sentence. > Ah, apologies. I didn't mean to suggest it wasn't important in your use case. > > The above is the sense in which I've been using the "timeout" term. > I see. You're using the word 'timeout' prescriptively (how a timeout is sometimes used) whereas I favor descriptive definitions (e.g. "A specified period of time that will be allowed to elapse in a system<http://en.wikipedia.org/wiki/System> before a specified event is to take place, unless another specified event occurs first" - a bullet on the same page). This could cause us to talk past one another. A timeout, IMO, essentially describes any race condition between a clock-based event (a certain time has been reached) and another input-based event. _______________________________________________ cap-talk mailing list [email protected] http://www.eros-os.org/mailman/listinfo/cap-talk