1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
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> To extend the explanation a little - the way we see things is this:
DM> - The server sets for MMORPGs and the like have to be secure - that means
DM> that any old Tom, Dick or Harry can't send a message directly to the economy
DM> service to tell it that they've just won the lottery :)
DM> - This means that the clients only have access to the front end services on
DM> the front end servers and that they don't have access to the naming service.
DM> (in order to connect to the front end services clients have to use the login
DM> service as a go-between... there are examples in our samples directory
DM> showing how this works)
DM> - So - the naming service runs on a smallish LAN that connects the game
DM> servers. It broadcasts messages like 'the xxx service has just arrived at
DM> address yyy' or 'the www service at address zzz has gone down/ disappeared'.
DM> These are cached by each service to keep an up to date address book of the
DM> other services that they can talk to.
DM> - In the normal way we don't see services being started or stopped as a very
DM> high frequency event.
DM> I hope this helps.
DM> Daniel.
DM> --------------------------------------------------------------------
DM> 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>
DM> Right, but in fact, we developed the system to fit our requirement for our
DM> game and in our system (in the shard), the naming service and all ther
DM> services are on a LAN, so we don't have high latency links.
DM> regards,
DM> Vianney Lecroart
DM> _______________________________________________
DM> Nel mailing list
DM> <A HREF="mailto:Nel@nevrax.org">Nel@nevrax.org</A>
DM> <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>
|
