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-June/000429.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to '')
| -rw-r--r-- | pipermail/nel/2001-June/000429.html | 70 |
1 files changed, 70 insertions, 0 deletions
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 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] More news from the nevrax teams...</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:lecroart%40nevrax.com"> + <LINK REL="Previous" HREF="000428.html"> + <LINK REL="Next" HREF="000430.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] More news from the nevrax teams...</H1> + <B>Vianney Lecroart</B> + <A HREF="mailto:lecroart%40nevrax.com" + TITLE="[Nel] More news from the nevrax teams...">lecroart@nevrax.com</A><BR> + <I>Thu, 21 Jun 2001 14:10:07 +0200</I> + <P><UL> + <LI> Previous message: <A HREF="000428.html">[Nel] More news from the nevrax teams...</A></li> + <LI> Next message: <A HREF="000430.html">[Nel] Re:More news from the nevrax teams...</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#429">[ date ]</a> + <a href="thread.html#429">[ thread ]</a> + <a href="subject.html#429">[ subject ]</a> + <a href="author.html#429">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello, + + +><i> I have a question about the caching for the naming service. You say it +</I>><i> automatically corrects caches when services move or are deleted. This +</I>><i> doesn't sound very scalable, it every client querying the name server +</I>><i> has to be contacted when something they asked about changed (especially +</I>><i> over high latency links). +</I> + +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: <A HREF="http://ace.planet-d.net">http://ace.planet-d.net</A> +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? + + + +</pre> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000428.html">[Nel] More news from the nevrax teams...</A></li> + <LI> Next message: <A HREF="000430.html">[Nel] Re:More news from the nevrax teams...</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#429">[ date ]</a> + <a href="thread.html#429">[ thread ]</a> + <a href="subject.html#429">[ subject ]</a> + <a href="author.html#429">[ author ]</a> + </LI> + </UL> +</body></html> |