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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Nel] Suggestion for the NeL network library / architecture</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:x5101920%40fedro.ugr.es">
<LINK REL="Previous" HREF="000081.html">
<LINK REL="Next" HREF="000083.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Nel] Suggestion for the NeL network library / architecture</H1>
<B>MIGUEL ANGEL BLANCH LARDIN</B>
<A HREF="mailto:x5101920%40fedro.ugr.es"
TITLE="[Nel] Suggestion for the NeL network library / architecture">x5101920@fedro.ugr.es</A><BR>
<I>Tue, 12 Dec 2000 11:48:18 +0100 (MET)</I>
<P><UL>
<LI> Previous message: <A HREF="000081.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
<LI> Next message: <A HREF="000083.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#82">[ date ]</a>
<a href="thread.html#82">[ thread ]</a>
<a href="subject.html#82">[ subject ]</a>
<a href="author.html#82">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>><i> That's where PGM/multicast intervenes. In that model, the agent,
</I>when he
><i> changes some of his variables, notifies the replica that "XYZ are
</I>now...".
><i> I spoke about how the world services organise where an agent
</I>resides. In
><i> some models, you have about one, maybe two replicas, which you can
</I>notify
><i> using a standard TCP stream. Or RDP. But, if you want a
</I>load-balancing
><i> system, you quickly end up with a replica of an object in most world
</I>><i> service processes. It becomes then more efficient to multicast the
</I>updates
><i> as above to all processes, and update them all in one sweep.
</I>
Ok, I always have though of load balancing as load-work division
between servers.
I think that the above kind of working can have several inconsistences
, just take a look to some distributed Mutual exclusion algos.
Just imagine that both copies of a object multicast different
positions, you have to choose what is the best one, and whatever your
choose is, it will be wrong, and servers can't be wrong.
Replycating work can be a real pain.
And for what you have said multicast isn't a solution for end-users.
I think that IPv6 will fix these things, by having a multicast in the
standart, isn't it?
</pre>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000081.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
<LI> Next message: <A HREF="000083.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#82">[ date ]</a>
<a href="thread.html#82">[ thread ]</a>
<a href="subject.html#82">[ subject ]</a>
<a href="author.html#82">[ author ]</a>
</LI>
</UL>
</body></html>
|
