[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

9424: [MUD-Dev] Sockets and fibers

[Full Header] [Plain Text]
From: "Caliban Tiresias Darklock" <caliban@darklock.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Wed, 20 Jan 1999 09:11:06 -0800
Organization: Kanga.Nu
Hopefully, this won't bounce. Once I get a message through, I'll pump
previous messages that bounced back through here. (Not your fault, name
server refresh problem on my end. Can't be helped.)

Has anyone here looked at the possibilities of spawning a single thread
which handles sockets and then using Microsoft's "fibers" to handle
individual sockets? How much of the one-thread-per-socket problem would be
solved by this? With the speed of modern computers, what are the real
problems with just serialising the socket handling -- one thread with all
the sockets, servicing each socket in turn for some small time slice?

Yes, I know, writing MUD servers under Windows is Bad. Granted. All the
same. ;)

| Caliban Tiresias Darklock            caliban@darklock.com
| Darklock Communications          http://www.darklock.com/
| U L T I M A T E   U N I V E R S E   I S   N O T   D E A D
| 774577496C6C6E457645727355626D4974H       -=CABAL::3146=-