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
|
<!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="000083.html">
<LINK REL="Next" HREF="000085.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 12:20:32 +0100 (MET)</I>
<P><UL>
<LI> Previous message: <A HREF="000083.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
<LI> Next message: <A HREF="000085.html">[Nel] Bugs on nevrax.org</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#84">[ date ]</a>
<a href="thread.html#84">[ thread ]</a>
<a href="subject.html#84">[ subject ]</a>
<a href="author.html#84">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>><i> Ahem, no. I might have used object and agent in various contexts,
</I>but
><i> an agent is the only one which is authorised to change its state.
</I>The
><i> other objects are "replica", or passive objects. Each agent may
</I>exist
><i> only as a single copy over the set of processes, and he is the
</I>entity
><i> responsible for updating the local states of the replica objects in
</I>><i> the other processes.
</I>><i>
</I>><i> If you want "what is your XYZ", the local replica answers. However,
</I>if
><i> you want "teleport to XYZ", the message is transmitted across the
</I>network
><i> to the unique agent, which updates its internal state, and then
</I>retransmits
><i> to all replicas "set internal state XYZ". And the latter is when
</I>multicast
><i> helps when there are many replicas to update.
</I>
Ok, as far as I am thinking about agents, a replica only show info but
can't process code. So all the modificators should be send to the
main agent, that then update.
There is still the possibility of an object to get two contradictory
updates at the same time. To avoid this you should order the messages,
something that I feel is unefficient and ugly.
Just image agent is a ball, and then two user decide to kick the two
replica of the agent, so the replicas get the kick commnand and send
it to the agent.
><i> > Replycating work can be a real pain.
</I>><i>
</I>><i> Hey, if I could buy a terahertz processor and have everything run on
</I>a
><i> single process, I'd be happy too :)
</I>
If you need a terahertz processor to run the server, you better start
again the design stage.
Just I want to note that replycanting the work can lead to ugly
things and race conditions.
</pre>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000083.html">[Nel] Suggestion for the NeL network library / architecture</A></li>
<LI> Next message: <A HREF="000085.html">[Nel] Bugs on nevrax.org</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#84">[ date ]</a>
<a href="thread.html#84">[ thread ]</a>
<a href="subject.html#84">[ subject ]</a>
<a href="author.html#84">[ author ]</a>
</LI>
</UL>
</body></html>
|
