April 1997
- From out of the shadows... Dan Mazeau
- Introduction Shawn Halpenny
- Introduction Nathan Yospe
- Introduction Chris Gray
- Introduction coder@ibm.net
- Introduction S001GMU@nova.wright.edu
- Introduction Jeff Kesselman
- Introduction Chris Gray
- Introduction Mik Clarke
- Introduction Caliban Tiresias Darklock
- Introduction Mik Clarke
- Introduction Caliban Tiresias Darklock
- Introduction J C Lawrence
- Introduction Elia Morling
- Event-driven? Michael Hohensee
- Event-driven? Nathan Yospe
- Event-driven? coder@ibm.net
- Event-driven? Jon A. Lambert
- Event-driven? Adam Wiggins
- Event-driven? Shawn Halpenny
- Event-driven? Chris Gray
- Event-driven? coder@ibm.net
- (subject missing) Dan Mazeau
- A late introduction Jon A. Lambert
- Re-Introduction S001GMU@nova.wright.edu
- New guy Walter Goodwin
- New guy coder@ibm.net
- Socket Stuff Shawn Halpenny
- database stuff Chris Gray
- So in an event-driven server, how do you ... Michael Hohensee
- So in an event-driven server, how do you ... Nathan Yospe
- So in an event-driven server, how do you ... S001GMU@nova.wright.edu
- So in an event-driven server, how do you ... Chris Gray
- So in an event-driven server, how do you ... clawrenc@xsvr1.cup.hp.com
- So in an event-driven server, how do you ... clawrenc@cup.hp.com
- Off on the languages tangent! Chris Gray
- Yet Another Introduction Reed D. Copsey, Jr.
- Yet Another Introduction Nathan Yospe
- Yet Another Introduction clawrenc@cup.hp.com
- Yet Another Introduction clawrenc@cup.hp.com
- Yet Another Introduction Adam Wiggins
- Yet Another Introduction Dmitri Kondratiev
- self-intro: Cynbe Cynbe ru Taren
- Unique id's Chris Gray
- Unique id's clawrenc@cup.hp.com
- Unique id's Jon A. Lambert
- Unique id's coder@ibm.net
- Unique id's Jon A. Lambert
- Unique id's coder@ibm.net
- Unique id's Jeff Kesselman
- Unique id's clawrenc@cup.hp.com
- Unique id's Jon A. Lambert
- Dupes are my fault (again) coder@ibm.net
- six degrees of submission ... er, compilation. Cynbe ru Taren
- six degrees of submission ... er, compilation. Jeff Kesselman
- Java as a mudserver language Cynbe ru Taren
- Java as a mudserver language Jeff Kesselman
- Execution Chris Gray
- Using system time for ObjectIDs clawrenc@cup.hp.com
- short absence Chris Gray
- short absence coder@ibm.net
- Hello! Ross Nicoll
- Ho hum (clarifiyign AI terms) Jeff Kesselman
- Ho hum Ling
- Ho hum Nathan Yospe
- Ho hum Jeff Kesselman
- Ho hum Ling
On Sat, 12 Apr 1997, Nathan Yospe wrote:
> On Sat, 12 Apr 1997, Ling wrote:
>
> Hmmm. Did any of us provide personal life stuff?
Dunno, I thought I'd provide those snippets of information so you guys
know my leanings and background. *shrug* The main bit being untrained
which means I like to think I've got the aptitude and intuition for coding
but I don't know all the computer jargon (there's a distinct trend to name
and patent anything which moves).
> :Nathan: How on earth does your intepreter conducts the risk assessment?
> :Eg:
> :> shoot rifle at tank
> :You sure?
> :> yes
> :You die but luckily it wasn't painful coz that one had the latest
> :vapouriser thingibob (manufactured by Grestel).
> :etc
>
> You mean, how does it decide to ask "you sure"? That's pretty simple.
> There is a probability weight on prefered interpretation of a command,
> with comparative risk being a crude product of action effectiveness and
> consequences. This is part of the command interpreter, and is tied
I would have thought that'll be fairly tough to calculate. Does it every
ask 'You sure?' when it's obviously a low risk action?
> :in reading through some of the old stuff. Just thought I'd bring the
> :topic of game design back into the mailing list and pollute the optic
> :fibres with my presence whilst I'm at it.
>
> Ah, now this is a fun debate. Personally, I like a system with feedback
> between a list of attributes and a list of skills, all of which are
Hmm.. I'll wait patiently for some development (like that Champion thing).
Gonna be busy for the immediate future...
Earlier, someone mentioned the possibility of the processor spending most
of it's time time-slicing between multiple threads if there was a lot of
connections. This number of threads business seems a lot like voodoo to
me and being the unsure vulnerable type (while I'm in this mailing list
watching all you masters chat), I won't mind some help. This is my model
and it'll be great if someone commented (it's for a uniprocessor):
Initial thread: Sets everything up, opens a socket, and waits to
terminate.
Signal thread: Sits in a sigwait() loop, handles signal for the entire
process.
Server thread: Waits for the next connection.
Input Socket thread: Snoozes on select(), gets input from socket and
plonks it in the input buffer, serves multiple sockets.
Output Socket thread: Waken up whenever there's something in the output
buffer.
Input processing threads: Multiple threads which interpret the actual
input, multiple meaning something like 1:10 ratio of
threads to clients.
Event processing threads: 3 threads sat in a pool (nicked from Lambert's
I think).
Area threads: The usual, I've not thought about this yet, it's gonna pose
a problem.
Compiler threads: Compiles I suppose...
The main focus is on the socket threads. I can either use the above or I
can: Combine the socket input and output threads by getting the signal
handler to wait for SIGIO, use select() to figure out which client(s) have
input pending and use semaphores to tell the appropriate threads, the
socket threads would sit in a semaphore wait position (the semaphore can
be released by the signal handler or be an event which has just popped
something in the output buffer).
The dilemma is: If I used select(), the socket threads will either have
to use a loop to check input and output buffers or I can have input and
output threads (the server thread can have SIGIO all to herself). If I
depend on SIGIO, I will have to end up using select() anyway to figure out
which socket it was and I may as well have one thread sleeping on
select(), waking up the other threads when needed. What gets me is that
if I used the later, won't there be an awfully high number of SIGIOs being
sent out?
*ponder*
PS: Thanx for the small bit of something about PCCTS, Jeff.
| "With my naked eyes I saw the falling"
_O_O_ Ling - Freshwater fish rain coming down on."
- Ho hum coder@ibm.net
- Ho hum coder@ibm.net
- Fw: Just a bit of musing Travis Casey
- Risk Assessment -- was (Ho hum) Jon A. Lambert
- Who is Steward and what can he do for me? Jon A. Lambert
- Who is Steward and what can he do for me? clawrenc@cup.hp.com
- Who is Steward and what can he do for me? Chris Gray
- project management (or coding, kings, and other things) Jon A. Lambert
- Threads and Sockets (Was Ho hum) S001GMU@nova.wright.edu
- Threads and Sockets (Was Ho hum) Jeff Kesselman
- Threads and Sockets (Was Ho hum) S001GMU@nova.wright.edu
- Threads and Sockets (Was Ho hum) clawrenc@cup.hp.com
- Threads and Sockets (Was Ho hum) Chris Gray
- Strings & Memory Usage Greg Munt
- Strings & Memory Usage clawrenc@cup.hp.com
- Strings & Memory Usage Jeff Kesselman
- Strings & Memory Usage Shawn Halpenny
- Strings & Memory Usage ashen
- Strings & Memory Usage Chris Gray
- Steward coder@ibm.net
- r.g.m.* - worthwhile thread Nathan Yospe
- r.g.m.* - worthwhile thread clawrenc@cup.hp.com
- r.g.m.* - worthwhile thread Jeff Kesselman
- r.g.m.* - worthwhile thread Chris Gray
- (fwd) A Mud Protocol (MUD Markup Language) coder@ibm.net
- Ho hum (Sockets) Ling
- Steward and other painful friends coder@ibm.net
- A Combat System (please critique!) S001GMU@nova.wright.edu
- Your Message To mud-dev Jon A. Lambert
- I'm back Chris Gray
- Changes to the list coder@ibm.net
- Oops coder@ibm.net
- Verb binding Chris Gray
- Verb binding clawrenc@cup.hp.com
- Verb binding ashen
- Verb binding Chris Gray
- Verb binding Adam Wiggins
- Verb binding clawrenc@cup.hp.com
- Verb binding S001GMU@nova.wright.edu
- Verb binding Shawn Halpenny
- Verb binding Chris Gray
- Verb binding clawrenc@cup.hp.com
- Verb binding Chris Gray
- Why have a combat state? Jeff Kesselman
- Why have a combat state? clawrenc@cup.hp.com
- Introduction Jamie Norrish
- Introduction S001GMU@nova.wright.edu
- Introduction clawrenc@cup.hp.com
- Introduction Jeff Kesselman
- Introduction clawrenc@cup.hp.com
- Introduction Chris Gray
- Introduction Travis Casey
- Introduction Jeff Kesselman
- Introduction scherecwich@angelfire.com
- Introduction Jon A. Lambert
- Introduction Chris Gray
- (fwd) Issues from the digests and Wout's list Raz
- (fwd) Issues from the digests and Wout's list Chris Gray
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- (fwd) Issues from the digests and Wout's list Raz
- (fwd) Issues from the digests and Wout's list Chris Gray
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- (fwd) Issues from the digests and Wout's list Chris Gray
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- (fwd) Issues from the digests and Wout's list Oliver Jowett
- (fwd) Issues from the digests and Wout's list Chris Gray
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- (fwd) Issues from the digests and Wout's list Raz
- (fwd) Issues from the digests and Wout's list Miroslav Silovic
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- (fwd) Issues from the digests and Wout's list Adam Wiggins
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- (fwd) Issues from the digests and Wout's list Miroslav Silovic
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- (fwd) Issues from the digests and Wout's list Raz
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- (fwd) Issues from the digests and Wout's list clawrenc@cup.hp.com
- Me Raz
- Sendmail changes coder@ibm.net
- Reposts Adam Wiggins
- Semaphores, Mutices, fd_sets Greg Munt
- Semaphores, Mutices, fd_sets Jeff Kesselman
- Semaphores, Mutices, fd_sets clawrenc@cup.hp.com
- MUD Design Digest V1 #55 coder@ibm.net
- Me Raz
- Magnetic Scrolls' magical parser Greg Munt
- Magnetic Scrolls' magical parser clawrenc@cup.hp.com
- Magnetic Scrolls' magical parser Adam Wiggins
- Magnetic Scrolls' magical parser Nathan Yospe
- Magnetic Scrolls' magical parser Chris Gray
- Magnetic Scrolls' magical parser Ling
- Magnetic Scrolls' magical parser Chris Gray
- Magnetic Scrolls' magical parser Shawn Halpenny
- Reposts Jeff Kesselman
- Email change Alex Oren
- SUBSCRIBE Alex Oren
- (fwd) Death in Muds -(also Birth, Imprisonment, Aging, and skill development) coder@ibm.net
- fd_set limitations Greg Munt
- parsing Chris Gray