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

Sat May 3 01:25:28 CEST 1997

This is a multi-part message in MIME format.

------=_NextPart_000_01BC5760.E21F24A0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

> From: Jeff Kesselman <jeffk at 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

------=_NextPart_000_01BC5760.E21F24A0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head></head><BODY bgcolor=3D"#FFFFFF"><p><font size=3D2 =
color=3D"#000000" face=3D"Times New Roman">> From: Jeff Kesselman =
<<font color=3D"#0000FF"><u>jeffk at tenetwork.com</u><font =
color=3D"#000000">><br>> Subject: [MUD-Dev]  Re: =
Multi-threaded mudding (was a flamefest)<br>> <br>> At 10:04 PM =
5/1/97 PST8PDT, you wrote:<br>> >Based on my definition of =
"event-driven", Cold would NOT classify.<br>> >It does =
have a 'dispatcher' which simulates time-slicing, <br>> >yet it =
doesn't dispatch events.  It only partially approaches this at the =
<br>> >network level only.  <br>> <br>> Um, I disagree. =
Cold does indeed dispatch events. The evnts are hard coded<br>> into =
the system and are as follows:<br>> (1) packet arrival<br>> (2) =
heartbeat<br>> (3) connection<br>> (4) conenction close<br>> =
<br>> There may be a few mreo im forgettting. in each case the event =
is<br>> dispatched in teh form of a method call to an object.<br>> =
<br>> If thsi doesnt fit your def of "event driven" then I =
tyhink yer beign way<br>> too selective in teh application of this =
term.<br>> <br><font size=3D2>This application relies on the OS to =
generate all its events.<br>More particularly the socket port and the =
system clock.<br>All applications that run on a Unix machine would then =
<br>classify as event driven taken collectively together as<br>a system. =
 Clearly not the intent of the distinction between<br>procedural =
and event driven.<br><br>You are describing:<br>Cold --- settimer event =
--->  OS<br>OS   --- timer event =
   ---> Cold<br><br>OS   --- Socket input =
event  ---> Cold<br>Cold --- Socket output event ---> =
OS<br><br>An event-driven system would need: <br>Cold =
            &=
nbsp;           &n=
bsp;  Cold<br>Subsystem/ ----???? event ----> =
Subsystem/<br>Object =
            &=
nbsp;           &n=
bsp;Object <br> =
            &=
nbsp;         <br><br>JL<br>=
<br><font size=3D2><br><br><br></p>
</font></font></font></font></font></body></html>
------=_NextPart_000_01BC5760.E21F24A0--