diff options
Diffstat (limited to 'pipermail/nel/2000-December/000079.html')
| -rw-r--r-- | pipermail/nel/2000-December/000079.html | 71 |
1 files changed, 71 insertions, 0 deletions
diff --git a/pipermail/nel/2000-December/000079.html b/pipermail/nel/2000-December/000079.html new file mode 100644 index 00000000..a10bb898 --- /dev/null +++ b/pipermail/nel/2000-December/000079.html @@ -0,0 +1,71 @@ +<!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="000077.html"> + <LINK REL="Next" HREF="000078.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 11:11:10 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000077.html">[Nel] Suggestion for the NeL network library / architecture</A></li> + <LI> Next message: <A HREF="000078.html">[Nel] Suggestion for the NeL network library / architecture</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#79">[ date ]</a> + <a href="thread.html#79">[ thread ]</a> + <a href="subject.html#79">[ subject ]</a> + <a href="author.html#79">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>According to Dim Segebart: +><i> Hello ! +</I>><i> Just one question. +</I>><i> +</I>><i> >From <A HREF="http://pgm.tibco.com/draft-speakman-pgm-spec-04.txt">http://pgm.tibco.com/draft-speakman-pgm-spec-04.txt</A> +</I>><i> >>> PGM runs over a datagram multicast protocol such as IP multicast [5]. +</I>><i> +</I>><i> AFAIK, many ISP's ban multicast traffic and many users'll be unable to use +</I>><i> software based on it. +</I>><i> Am I wrong or missing something ? +</I>><i> TIA +</I> +And Jean-Noel Moyne said: +><i> network transport for your messaging. That need being for server to +</I>><i> server communication, not server to client. +</I> +Note "server to server". What Jean-Noel was suggesting was not a protocol +to communicate with the clients, but a protocol to communicate between +the various servers that constitute a world cluster. + +Since these clusters will be located in a single facility, on a dedicated +switch, the issue of IP filtering do not apply :) + +-- +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="000077.html">[Nel] Suggestion for the NeL network library / architecture</A></li> + <LI> Next message: <A HREF="000078.html">[Nel] Suggestion for the NeL network library / architecture</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#79">[ date ]</a> + <a href="thread.html#79">[ thread ]</a> + <a href="subject.html#79">[ subject ]</a> + <a href="author.html#79">[ author ]</a> + </LI> + </UL> +</body></html> |