diff options
Diffstat (limited to '')
| -rw-r--r-- | pipermail/nel/2000-December/000084.html | 89 |
1 files changed, 89 insertions, 0 deletions
diff --git a/pipermail/nel/2000-December/000084.html b/pipermail/nel/2000-December/000084.html new file mode 100644 index 00000000..0d5d29f9 --- /dev/null +++ b/pipermail/nel/2000-December/000084.html @@ -0,0 +1,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> |