<!-- MHonArc v2.4.4 -->
<!--X-Subject: Threads and Sockets (Was Ho hum) -->
<!--X-From-R13: E001U[GNabin.jevtug.rqh -->
<!--X-Date: from babe.globecomm.net [207.51.48.8] by mx4.ibm.net id 861051303.24688-1 Mon Apr 14 20:55:03 1997 -->
<!--X-Message-Id: 01IHP5FUJZMQ986Q2G#nova,wright.edu -->
<!--X-Content-Type: text/plain -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, Threads and Sockets (Was Ho hum)</title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:S001GMU#nova,wright.edu">
</head>
<body background="/backgrounds/paperback.gif" bgcolor="#ffffff"
text="#000000" link="#0000FF" alink="#FF0000" vlink="#006000">
<font size="+4" color="#804040">
<strong><em>MUD-Dev<br>mailing list archive</em></strong>
</font>
<br>
[ <a href="../">Other Periods</a>
| <a href="../../">Other mailing lists</a>
| <a href="/search.php3">Search</a>
]
<br clear=all><hr>
<!--X-Body-Begin-->
<!--X-User-Header-->
<!--X-User-Header-End-->
<!--X-TopPNI-->
Date:
[ <a href="msg00135.html">Previous</a>
| <a href="msg00137.html">Next</a>
]
Thread:
[ <a href="msg00293.html">Previous</a>
| <a href="msg00139.html">Next</a>
]
Index:
[ <A HREF="author.html#00136">Author</A>
| <A HREF="#00136">Date</A>
| <A HREF="thread.html#00136">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>Threads and Sockets (Was Ho hum)</H1>
<HR>
<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->
<UL>
<LI><em>To</em>: <A HREF="mailto:mud-dev#null,net">mud-dev#null,net</A></LI>
<LI><em>Subject</em>: Threads and Sockets (Was Ho hum)</LI>
<LI><em>From</em>: <A HREF="mailto:S001GMU#nova,wright.edu">S001GMU#nova,wright.edu</A></LI>
<LI><em>Date</em>: Mon, 14 Apr 1997 14:19:40 -0400 (EDT)</LI>
</UL>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<HR>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<PRE>
just a thought that someone got stuck in my head.
I know threads are less expensive than full process switching, but isn't using
threads of the main program for handling I/O kinda dangerous? If the sockets
or any I/O bombs, down comes the whole program, or if the program goes down,
everyone gets dropped from the game. I've been leaning towards a
multi-processesing, multi-threaded environment where *most* of the mechanics
are grouped into one process that is threaded and all the file I/O and socket
Handling is done with other processes (possibly also threaded). That way, if
one process crashes the rest can keep plugging along or (in the case of the
game crashing and the socket process still running) tell the players that the
mud is experienceing technical difficulties (after some timeout period
expires). I use the message queue system to communicate among the processes,
mainly because it lends itself nicely to an event driven system and packaging
commands and info into discrete units (which I prefer to deal with).
As I sed, just a thought. ;)
-Greg
</PRE>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<HR>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg00135.html">Strings & Memory Usage</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00137.html">Re: Issues from the digests and Wout's list</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00293.html">Re: Issues from the digests and Wout's list</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00139.html">Re: Threads and Sockets (Was Ho hum)</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00136"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00136"><STRONG>Thread</STRONG></A></LI>
</UL>
</LI>
</UL>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
<ul><li>Thread context:
<BLOCKQUOTE><UL>
<LI><STRONG>Re: Issues from the digests and Wout's list</STRONG>, <EM>(continued)</EM>
<ul compact>
<LI><strong><A NAME="00181" HREF="msg00181.html">Re: Issues from the digests and Wout's list</A></strong>,
Orion Henry <a href="mailto:ohenry#sdcc10,ucsd.edu">ohenry#sdcc10,ucsd.edu</a>, Tue 22 Apr 1997, 17:17 GMT
<UL>
<LI><strong><A NAME="00190" HREF="msg00190.html">Re: [MUD-Dev] Re: Issues from the digests and Wout's list</A></strong>,
clawrenc <a href="mailto:clawrenc#cup,hp.com">clawrenc#cup,hp.com</a>, Thu 24 Apr 1997, 00:00 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00182" HREF="msg00182.html">Re: Issues from the digests and Wout's list</A></strong>,
clawrenc <a href="mailto:clawrenc#cup,hp.com">clawrenc#cup,hp.com</a>, Tue 22 Apr 1997, 20:31 GMT
</LI>
<LI><strong><A NAME="00293" HREF="msg00293.html">Re: Issues from the digests and Wout's list</A></strong>,
S001GMU <a href="mailto:S001GMU#nova,wright.edu">S001GMU#nova,wright.edu</a>, Wed 30 Apr 1997, 01:55 GMT
</LI>
</ul>
</LI>
<LI><strong><A NAME="00136" HREF="msg00136.html">Threads and Sockets (Was Ho hum)</A></strong>,
S001GMU <a href="mailto:S001GMU#nova,wright.edu">S001GMU#nova,wright.edu</a>, Tue 15 Apr 1997, 03:55 GMT
<UL>
<li><Possible follow-up(s)><br>
<LI><strong><A NAME="00139" HREF="msg00139.html">Re: Threads and Sockets (Was Ho hum)</A></strong>,
Jeff Kesselman <a href="mailto:jeffk#tenetwork,com">jeffk#tenetwork,com</a>, Tue 15 Apr 1997, 10:09 GMT
</LI>
<LI><strong><A NAME="00140" HREF="msg00140.html">Re: Threads and Sockets (Was Ho hum)</A></strong>,
S001GMU <a href="mailto:S001GMU#nova,wright.edu">S001GMU#nova,wright.edu</a>, Tue 15 Apr 1997, 20:33 GMT
</LI>
<LI><strong><A NAME="00143" HREF="msg00143.html">Re: Threads and Sockets (Was Ho hum)</A></strong>,
clawrenc <a href="mailto:clawrenc#cup,hp.com">clawrenc#cup,hp.com</a>, Tue 15 Apr 1997, 23:07 GMT
</LI>
<LI><strong><A NAME="00168" HREF="msg00168.html">Re: Threads and Sockets (Was Ho hum)</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Mon 21 Apr 1997, 04:09 GMT
</LI>
</UL>
</LI>
</UL></BLOCKQUOTE>
</ul>
<hr>
<center>
[ <a href="../">Other Periods</a>
| <a href="../../">Other mailing lists</a>
| <a href="/search.php3">Search</a>
]
</center>
<hr>
</body>
</html>