[MUD-Dev] [TECH] Event Queue System

Blane Bramble bbramble at montavista.co.uk
Wed Feb 20 09:35:09 CET 2002


J C Lawrence wrote:
> On Thu, 14 Feb 2002 17:02:32 -0600 
> the sage <the_sage2000 at juno.com> wrote:

>> 1) Has anyone implemented an event queue system and can give me
>> advise on doing it?

> Note: This is an abuse of the definition of "event".
> Unfortunately its an abuse I popularised in the early days of this
> list, and it doesn't seem willing to die.  It should die.

But could you not consider the external timer to be an event in
itself?

>  An event is an external state change whose detection prompts and
>  requires some form of reaction by the system, typically in the
>  form of an internal state change or internal process execution.

>    Translation: Something happened outside the system and the
>    system noticed and reacted in some way.  The thing that was
>    noticed was an "event".

> This is why things like key presses, network packets, interrupts,
> mouse movements etc are typically termed "events".  What you are
> calling events above and below are really just scheduled
> processes, very akin to cron jobs, not events.

A timer is usually based upon some form of interrupt and so can be
considered an event by this definition. The individual tasks
themselves of course are not events...

Blane (being difficult).


_______________________________________________
MUD-Dev mailing list
MUD-Dev at kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev



More information about the mud-dev-archive mailing list