<!-- MHonArc v2.4.4 -->
<!--X-Subject: Net protocols for MUDing -->
<!--X-From-R13: f001tzhNabin.jevtug.rqh -->
<!--X-Date: Tue, 24 Feb 1998 14:56:02 +0000 -->
<!--X-Message-Id: Pine.PMDF.3.95.980224094214.543402897A-100000#nova,wright.edu -->
<!--X-Content-Type: text/plain -->
<!--X-Reference: 9802240431.8uzf@ami-cg.GraySage.Edmonton.AB.CA -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, Net protocols for MUDing</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="msg00578.html">Previous</a>
| <a href="msg00580.html">Next</a>
]
Thread:
[ <a href="msg00576.html">Previous</a>
| <a href="msg00581.html">Next</a>
]
Index:
[ <A HREF="author.html#00579">Author</A>
| <A HREF="#00579">Date</A>
| <A HREF="thread.html#00579">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>Net protocols for MUDing</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>: Net protocols for MUDing</LI>
<LI><em>From</em>: <A HREF="mailto:s001gmu#nova,wright.edu">s001gmu#nova,wright.edu</A></LI>
<LI><em>Date</em>: Tue, 24 Feb 1998 09:54:07 -0500 (EST)</LI>
</UL>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<HR>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<PRE>
On Tue, 24 Feb 1998, Chris Gray wrote:
> [Chris L:]
>
> :The key feature of TCP which I'd remove would be the error correction.
> :Given a predictive client its both unecessary and counter-productive.
>
> Only to a certain extent. Sure, you can probably cruise over a bit of lost
> data in graphics or audio output. Missing some text from the middle of
> a paragraph could be a bit shocking to the average user, however. Also,
> the channel back from the client to the server should not lose any of
> the user's input. What you want is the ability to be sure that if a
> message arrives, then it is the complete message that was sent, not some
> fragment of one. You will also want to do your own checks on any header
> of the message, since UDP doesn't even guarantee correctness. (It typically
> is correct over ethernet, because of the way ethernet works, but it isn't
> over SLIP, for example, which is one reason why you shouldn't run NFS
> over a SLIP link.)
>
> If the system gets a bit smarter, with some caching in the client, then
> some sort of reliable protocol will be needed, both ways, to co-ordinate
> that cache.
It occurs to me that if you tie together the idea of using UDP connections
with the proposed mud markup language in another thread (<SMELL1> ...
</SMELL1>, etc), you could easily chop the paragraph into Data Packets,
based on the already defined sections of the paragraph. As long as each
complete section is recieved before the player sees any of it, it should
look reasonably acceptable to a player. If one or two sections come in a
little later, *shrug*, no biggie. The client will just add that layer of
resolution as it becomes available. I'm reminded of the way some pictures
on the web load, by first drawing large blocks and then redrawing with
smaller and smaller blocks until individual pixels are drawn. Maybe a
more appropriate analogy would be the original King's Quest, where it
would draw in pieces of the image until the whole scene was drawn.
-Greg
</PRE>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<HR>
<!--X-Follow-Ups-End-->
<!--X-References-->
<UL><LI><STRONG>References</STRONG>:
<UL>
<LI><STRONG><A NAME="00576" HREF="msg00576.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></STRONG>
<UL><LI><EM>From:</EM> cg#ami-cg,GraySage.Edmonton.AB.CA (Chris Gray)</LI></UL></LI>
</UL></LI></UL>
<!--X-References-End-->
<!--X-BotPNI-->
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg00578.html">Re: [MUD-Dev] The MLI Project</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00580.html">Re: [MUD-Dev] The MLI Project</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00576.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00581.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00579"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00579"><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: [MUD-Dev] The MLI Project</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<LI><strong><A NAME="00769" HREF="msg00769.html">Re: [MUD-Dev] The MLI Project</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Thu 19 Mar 1998, 22:08 GMT
</LI>
</ul>
</ul>
</ul>
<LI><strong><A NAME="00603" HREF="msg00603.html">Re: [MUD-Dev] The MLI Project</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Thu 26 Feb 1998, 07:06 GMT
</LI>
<LI><strong><A NAME="00606" HREF="msg00606.html">RE: [MUD-Dev] The MLI Project</A></strong>,
Koster, Raph <a href="mailto:rkoster#origin,ea.com">rkoster#origin,ea.com</a>, Thu 26 Feb 1998, 15:17 GMT
</LI>
</ul>
</LI>
<LI><strong><A NAME="00576" HREF="msg00576.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Tue 24 Feb 1998, 09:35 GMT
<UL>
<LI><strong><A NAME="00579" HREF="msg00579.html">Net protocols for MUDing</A></strong>,
s001gmu <a href="mailto:s001gmu#nova,wright.edu">s001gmu#nova,wright.edu</a>, Tue 24 Feb 1998, 14:56 GMT
</LI>
<LI><strong><A NAME="00581" HREF="msg00581.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
Caliban Tiresias Darklock <a href="mailto:caliban#darklock,com">caliban#darklock,com</a>, Tue 24 Feb 1998, 18:54 GMT
<UL>
<LI><strong><A NAME="00767" HREF="msg00767.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Thu 19 Mar 1998, 20:36 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00766" HREF="msg00766.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Thu 19 Mar 1998, 20:22 GMT
</LI>
</UL>
<UL>
<li><Possible follow-up(s)><br>
<LI><strong><A NAME="00645" HREF="msg00645.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Sat 28 Feb 1998, 18:04 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>
