diff options
Diffstat (limited to 'pipermail/nel/2001-June/000430.html')
| -rw-r--r-- | pipermail/nel/2001-June/000430.html | 90 |
1 files changed, 90 insertions, 0 deletions
diff --git a/pipermail/nel/2001-June/000430.html b/pipermail/nel/2001-June/000430.html new file mode 100644 index 00000000..bf352cf3 --- /dev/null +++ b/pipermail/nel/2001-June/000430.html @@ -0,0 +1,90 @@ +<!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:miller%40nevrax.com"> + <LINK REL="Previous" HREF="000429.html"> + <LINK REL="Next" HREF="000431.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] Re:More news from the nevrax teams...</H1> + <B>Daniel Miller</B> + <A HREF="mailto:miller%40nevrax.com" + TITLE="[Nel] Re:More news from the nevrax teams...">miller@nevrax.com</A><BR> + <I>Thu, 21 Jun 2001 18:47:37 +0200</I> + <P><UL> + <LI> Previous message: <A HREF="000429.html">[Nel] More news from the nevrax teams...</A></li> + <LI> Next message: <A HREF="000431.html">[Nel] Re:More news from the nevrax teams...</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#430">[ date ]</a> + <a href="thread.html#430">[ thread ]</a> + <a href="subject.html#430">[ subject ]</a> + <a href="author.html#430">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>To extend the explanation a little - the way we see things is this: + +- The server sets for MMORPGs and the like have to be secure - that means +that any old Tom, Dick or Harry can't send a message directly to the economy +service to tell it that they've just won the lottery :) + +- This means that the clients only have access to the front end services on +the front end servers and that they don't have access to the naming service. +(in order to connect to the front end services clients have to use the login +service as a go-between... there are examples in our samples directory +showing how this works) + +- So - the naming service runs on a smallish LAN that connects the game +servers. It broadcasts messages like 'the xxx service has just arrived at +address yyy' or 'the www service at address zzz has gone down/ disappeared'. +These are cached by each service to keep an up to date address book of the +other services that they can talk to. + +- In the normal way we don't see services being started or stopped as a very +high frequency event. + +I hope this helps. + +Daniel. + + +-------------------------------------------------------------------- +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 + + +</pre> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000429.html">[Nel] More news from the nevrax teams...</A></li> + <LI> Next message: <A HREF="000431.html">[Nel] Re:More news from the nevrax teams...</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#430">[ date ]</a> + <a href="thread.html#430">[ thread ]</a> + <a href="subject.html#430">[ subject ]</a> + <a href="author.html#430">[ author ]</a> + </LI> + </UL> +</body></html> |