Re: [MUD-Dev] Re: Multi-threaded mudding (was a flamefest)

["Jon A. Lambert" <jlsysinc#ix,netcom.com>]

> From: Jeff Kesselman <jeffk#tenetwork,com>
> Subject: [MUD-Dev]  Re: Multi-threaded mudding (was a flamefest)
>
> At 10:04 PM 5/1/97 PST8PDT, you wrote:
> >Based on my definition of "event-driven", Cold would NOT classify.
> >It does have a 'dispatcher' which simulates time-slicing,
> >yet it doesn't dispatch events.  It only partially approaches this at the
> >network level only.  
>
> Um, I disagree. Cold does indeed dispatch events. The evnts are hard coded
> into the system and are as follows:
> (1) packet arrival
> (2) heartbeat
> (3) connection
> (4) conenction close
>
> There may be a few mreo im forgettting. in each case the event is
> dispatched in teh form of a method call to an object.
>
> If thsi doesnt fit your def of "event driven" then I tyhink yer beign way
> too selective in teh application of this term.
>
This application relies on the OS to generate all its events.
More particularly the socket port and the system clock.
All applications that run on a Unix machine would then
classify as event driven taken collectively together as
a system.  Clearly not the intent of the distinction between
procedural and event driven.

You are describing:
Cold --- settimer event --->  OS
OS   --- timer event    ---> Cold

OS   --- Socket input event  ---> Cold
Cold --- Socket output event ---> OS

An event-driven system would need:
Cold                            Cold
Subsystem/ ----???? event ----> Subsystem/
Object                          Object
                      

JL