diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2000-December/000083.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to '')
| -rw-r--r-- | pipermail/nel/2000-December/000083.html | 72 |
1 files changed, 72 insertions, 0 deletions
diff --git a/pipermail/nel/2000-December/000083.html b/pipermail/nel/2000-December/000083.html new file mode 100644 index 00000000..6a8ba32a --- /dev/null +++ b/pipermail/nel/2000-December/000083.html @@ -0,0 +1,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: +><i> Just imagine that both copies of a object multicast different +</I>><i> positions, you have to choose what is the best one, and whatever your +</I>><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 "replica", 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 "what is your XYZ", the local replica answers. However, if +you want "teleport to XYZ", the message is transmitted across the network +to the unique agent, which updates its internal state, and then retransmits +to all replicas "set internal state XYZ". And the latter is when multicast +helps when there are many replicas to update. + +><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> |