aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-June/000431.html
diff options
context:
space:
mode:
authorneodarz <neodarz@neodarz.net>2018-08-11 20:21:34 +0200
committerneodarz <neodarz@neodarz.net>2018-08-11 20:21:34 +0200
commit0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch)
tree2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-June/000431.html
downloadnevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz
nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip
Initial commit
Diffstat (limited to 'pipermail/nel/2001-June/000431.html')
-rw-r--r--pipermail/nel/2001-June/000431.html107
1 files changed, 107 insertions, 0 deletions
diff --git a/pipermail/nel/2001-June/000431.html b/pipermail/nel/2001-June/000431.html
new file mode 100644
index 00000000..bc34d337
--- /dev/null
+++ b/pipermail/nel/2001-June/000431.html
@@ -0,0 +1,107 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Nel] Re:More news from the nevrax teams...</TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:zager%40teleaction.com">
+ <LINK REL="Previous" HREF="000430.html">
+ <LINK REL="Next" HREF="000441.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Nel] Re:More news from the nevrax teams...</H1>
+ <B>Dim Segebart</B>
+ <A HREF="mailto:zager%40teleaction.com"
+ TITLE="[Nel] Re:More news from the nevrax teams...">zager@teleaction.com</A><BR>
+ <I>Thu, 21 Jun 2001 19:33:30 +0200</I>
+ <P><UL>
+ <LI> Previous message: <A HREF="000430.html">[Nel] Re:More news from the nevrax teams...</A></li>
+ <LI> Next message: <A HREF="000441.html">[Nel] Congratulations + concerns</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#431">[ date ]</a>
+ <a href="thread.html#431">[ thread ]</a>
+ <a href="subject.html#431">[ subject ]</a>
+ <a href="author.html#431">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>It makes sense.
+Thank you.
+
+Thursday, June 21, 2001, 6:47:37 PM, you wrote:
+
+DM&gt; To extend the explanation a little - the way we see things is this:
+
+DM&gt; - The server sets for MMORPGs and the like have to be secure - that means
+DM&gt; that any old Tom, Dick or Harry can't send a message directly to the economy
+DM&gt; service to tell it that they've just won the lottery :)
+
+DM&gt; - This means that the clients only have access to the front end services on
+DM&gt; the front end servers and that they don't have access to the naming service.
+DM&gt; (in order to connect to the front end services clients have to use the login
+DM&gt; service as a go-between... there are examples in our samples directory
+DM&gt; showing how this works)
+
+DM&gt; - So - the naming service runs on a smallish LAN that connects the game
+DM&gt; servers. It broadcasts messages like 'the xxx service has just arrived at
+DM&gt; address yyy' or 'the www service at address zzz has gone down/ disappeared'.
+DM&gt; These are cached by each service to keep an up to date address book of the
+DM&gt; other services that they can talk to.
+
+DM&gt; - In the normal way we don't see services being started or stopped as a very
+DM&gt; high frequency event.
+
+DM&gt; I hope this helps.
+
+DM&gt; Daniel.
+
+
+DM&gt; --------------------------------------------------------------------
+DM&gt; Hello,
+
+
+&gt;&gt;<i> I have a question about the caching for the naming service. You say it
+</I>&gt;&gt;<i> automatically corrects caches when services move or are deleted. This
+</I>&gt;&gt;<i> doesn't sound very scalable, it every client querying the name server
+</I>&gt;&gt;<i> has to be contacted when something they asked about changed (especially
+</I>&gt;&gt;<i> over high latency links).
+</I>
+
+DM&gt; Right, but in fact, we developed the system to fit our requirement for our
+DM&gt; game and in our system (in the shard), the naming service and all ther
+DM&gt; services are on a LAN, so we don't have high latency links.
+
+DM&gt; regards,
+
+DM&gt; Vianney Lecroart
+
+DM&gt; _______________________________________________
+DM&gt; Nel mailing list
+DM&gt; <A HREF="mailto:Nel@nevrax.org">Nel@nevrax.org</A>
+DM&gt; <A HREF="http://www.nevrax.org/mailman/listinfo.cgi/nel">http://www.nevrax.org/mailman/listinfo.cgi/nel</A>
+
+
+
+--
+Dim Segebart mailto:<A HREF="mailto:zager@teleaction.de">zager@teleaction.de</A>
+
+
+
+</pre>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI> Previous message: <A HREF="000430.html">[Nel] Re:More news from the nevrax teams...</A></li>
+ <LI> Next message: <A HREF="000441.html">[Nel] Congratulations + concerns</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#431">[ date ]</a>
+ <a href="thread.html#431">[ thread ]</a>
+ <a href="subject.html#431">[ subject ]</a>
+ <a href="author.html#431">[ author ]</a>
+ </LI>
+ </UL>
+</body></html>