From 0ea5fc66924303d1bf73ba283a383e2aadee02f2 Mon Sep 17 00:00:00 2001 From: neodarz Date: Sat, 11 Aug 2018 20:21:34 +0200 Subject: Initial commit --- pipermail/nel/2001-June/000429.html | 70 +++++++++++++++++++++++++++++++++++++ 1 file changed, 70 insertions(+) create mode 100644 pipermail/nel/2001-June/000429.html (limited to 'pipermail/nel/2001-June/000429.html') diff --git a/pipermail/nel/2001-June/000429.html b/pipermail/nel/2001-June/000429.html new file mode 100644 index 00000000..92ec07e7 --- /dev/null +++ b/pipermail/nel/2001-June/000429.html @@ -0,0 +1,70 @@ + + + + [Nel] More news from the nevrax teams... + + + + + + +

[Nel] More news from the nevrax teams...

+ Vianney Lecroart + lecroart@nevrax.com
+ Thu, 21 Jun 2001 14:10:07 +0200 +

+
+ +
Hello,
+
+
+> I have a question about the caching for the naming service. You say it
+> automatically corrects caches when services move or are deleted. This
+> doesn't sound very scalable, it every client querying the name server
+> has to be contacted when something they asked about changed (especially
+> over high latency links).
+
+
+Right, but in fact, we developed the system to fit our requirement for our
+game and in our system (in the shard), the naming service and all  ther
+services are on a LAN, so we don't have high latency links.
+
+regards,
+
+Vianney Lecroart
+---
+lead network programmer / nevrax.com
+icq#: 6870415
+homepage: http://ace.planet-d.net
+www.geekcode.com: GCS/E d- s+++: a-- C+++$ UL++ P- L+++>+$ E+>- W++ N+ o? K-
+w++$ O- M- V- PS- PE? Y PGP t 5? X+ R- tv++ b- DI D+ G e++ h+ r-- y?
+
+
+
+
+ + + +
+

+ -- cgit v1.2.1