On May-25, Dan Sugalski wrote:
> At 10:31 AM +0200 5/25/04, Leopold Toetsch wrote:
> >Dan Sugalski <[EMAIL PROTECTED]> wrote:
> >> An unsolicited event, on the other hand, is one that parrot generates
> >> as the result of something happening external to itself, or as the
> >> result of some recurring event happening. Signals and GUI events, for
> >> example, are unsolicted as are recurring timer events.
> >
> >I don't think that there is much difference between these two types of
> >events. You don't get signals if you don't do the appropriate sigaction
> >call. You ask the OS for an one-shot timer or for a recurring one, so
> >you'll get one or more events. That's all known.
>
> The difference there is that a solicited event is one you have asked
> for *and* received an event/request object for, so you can identify
> the request/event as it makes its way through a stream. You can't do
> that with the unsolicited ones, since you don't know they exist until
> they've shown up.
Perhaps that's a better thing to use to describe them, then. I
understand the intuitive difference between expected/unexpected or
solicited/unsolicited, but upon closer examination that particular
difference gets really fuzzy. Perhaps registered/unregistered? You
really want to say that you have a handle ("event"? "object"?)
associated with your solicited event, but I don't know how to turn
that into an adjective. Preallocated? Prepared? Identified? Labeled?
Named? Tracked? Hey, that last one might work.
