aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2000-December/000083.html
blob: 6a8ba32ad1c7ff5b710a8afeb49476c27ec2d50f (plain)
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
<!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:archer%40nevrax.com">
   <LINK REL="Previous"  HREF="000082.html">
   <LINK REL="Next" HREF="000084.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Nel] Suggestion for the NeL network library / architecture</H1>
    <B>Vincent Archer</B> 
    <A HREF="mailto:archer%40nevrax.com"
       TITLE="[Nel] Suggestion for the NeL network library / architecture">archer@nevrax.com</A><BR>
    <I>Tue, 12 Dec 2000 12:11:26 +0100</I>
    <P><UL>
        <LI> Previous message: <A HREF="000082.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
        <LI> Next message: <A HREF="000084.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#83">[ date ]</a>
              <a href="thread.html#83">[ thread ]</a>
              <a href="subject.html#83">[ subject ]</a>
              <a href="author.html#83">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>According to MIGUEL ANGEL BLANCH LARDIN:
&gt;<i> Just imagine that both copies of a object multicast different 
</I>&gt;<i> positions, you have to choose what is the best one, and whatever your 
</I>&gt;<i> choose is, it will be wrong, and servers can't be wrong.
</I>
Ahem, no. I might have used object and agent in various contexts, but
an agent is the only one which is authorised to change its state. The
other objects are &quot;replica&quot;, or passive objects. Each agent may exist
only as a single copy over the set of processes, and he is the entity
responsible for updating the local states of the replica objects in
the other processes.

If you want &quot;what is your XYZ&quot;, the local replica answers. However, if
you want &quot;teleport to XYZ&quot;, the message is transmitted across the network
to the unique agent, which updates its internal state, and then retransmits
to all replicas &quot;set internal state XYZ&quot;. And the latter is when multicast
helps when there are many replicas to update.

&gt;<i> Replycating work can be a real pain.
</I>
Hey, if I could buy a terahertz processor and have everything run on a
single process, I'd be happy too :)

-- 
Vincent Archer                                         Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A>

Nevrax France.                              Off on the yellow brick road we go!

</pre>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI> Previous message: <A HREF="000082.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
	<LI> Next message: <A HREF="000084.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#83">[ date ]</a>
              <a href="thread.html#83">[ thread ]</a>
              <a href="subject.html#83">[ subject ]</a>
              <a href="author.html#83">[ author ]</a>
         </LI>
       </UL>
</body></html>