diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-July/000492.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-July/000492.html')
| -rw-r--r-- | pipermail/nel/2001-July/000492.html | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/pipermail/nel/2001-July/000492.html b/pipermail/nel/2001-July/000492.html new file mode 100644 index 00000000..f548b9c8 --- /dev/null +++ b/pipermail/nel/2001-July/000492.html @@ -0,0 +1,63 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] TCP vs. UDP</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:v.caron%40zerodeux.net"> + <LINK REL="Previous" HREF="000489.html"> + <LINK REL="Next" HREF="000494.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] TCP vs. UDP</H1> + <B>Vincent Caron</B> + <A HREF="mailto:v.caron%40zerodeux.net" + TITLE="[Nel] TCP vs. UDP">v.caron@zerodeux.net</A><BR> + <I>Fri, 06 Jul 2001 20:21:51 +0200</I> + <P><UL> + <LI> Previous message: <A HREF="000489.html">[Nel] TCP vs. UDP</A></li> + <LI> Next message: <A HREF="000494.html">[Nel] TCP vs. UDP</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#492">[ date ]</a> + <a href="thread.html#492">[ thread ]</a> + <a href="subject.html#492">[ subject ]</a> + <a href="author.html#492">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>><i> Btw, you cannot "design your own layer", because you need to use the +</I>><i> existing internet to send your data (which will only accept UDP and TCP). +</I>><i> However, they probably did add to UDP, by adding an extra software layer to +</I>><i> provide "reliable udp" (its almost trivial to do). +</I> +But do you need 'reliable transmission' ? Lost or delayed packets are +part of the rules, couldn't you take this into account in your network +and game code design ? Have a look at the streaming pb and protocols +such as RTP or RTSP, they deal with the pb of 1) time sync and 2) data +loss. This is sometime perfectly acceptable to loose some info in +a game and replace it with interpolated data until getting back in +sync. + +</pre> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000489.html">[Nel] TCP vs. UDP</A></li> + <LI> Next message: <A HREF="000494.html">[Nel] TCP vs. UDP</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#492">[ date ]</a> + <a href="thread.html#492">[ thread ]</a> + <a href="subject.html#492">[ subject ]</a> + <a href="author.html#492">[ author ]</a> + </LI> + </UL> +</body></html> |