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/2001-December/000817.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/2001-December/000817.html | 80 |
1 files changed, 80 insertions, 0 deletions
diff --git a/pipermail/nel/2001-December/000817.html b/pipermail/nel/2001-December/000817.html new file mode 100644 index 00000000..f894930b --- /dev/null +++ b/pipermail/nel/2001-December/000817.html @@ -0,0 +1,80 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] server architecture (front end, load balancing, login service, ....)</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:cblt%40cblt.org"> + <LINK REL="Previous" HREF="000815.html"> + <LINK REL="Next" HREF="000825.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] server architecture (front end, load balancing, login service, ....)</H1> + <B>Nicolas Hognon</B> + <A HREF="mailto:cblt%40cblt.org" + TITLE="[Nel] server architecture (front end, load balancing, login service, ....)">cblt@cblt.org</A><BR> + <I>Fri, 14 Dec 2001 20:11:43 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000815.html">[Nel] RE: GPL confusion</A></li> + <LI> Next message: <A HREF="000825.html">[Nel] server architecture (front end, load balancing, login service, ....)</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#817">[ date ]</a> + <a href="thread.html#817">[ thread ]</a> + <a href="subject.html#817">[ subject ]</a> + <a href="author.html#817">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello .... + +I've got a little question about the architecture of the server side. +If I don't make mistake a shard is composed of N front ends and behind +front ends there is some computers running different services. +And some where there is a login service (one per shard or one for all shard +?) + +Clients communicate with one front end of a shard. + +But how clients are balanced between the N front ends of a shard ? +It will be done by a generic load balancer (hardware) +or a specific service from NEL ? + +The source code of the load balancer and the front end are delivered with +NEL ? + +If there a description of all NEL services ? +what is the welcome service ? + +sorry for all this questions .... +bye + +-- +Nicolas Hognon +<A HREF="mailto:nicolash@virtools.com">nicolash@virtools.com</A> + +Virtools - The Behavior Company +Tel. (+33) 1 42 71 46 86 / Fax. (+33) 1 42 71 86 53 +<A HREF="http://www.virtools.com/">http://www.virtools.com/</A> + + + +</pre> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000815.html">[Nel] RE: GPL confusion</A></li> + <LI> Next message: <A HREF="000825.html">[Nel] server architecture (front end, load balancing, login service, ....)</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#817">[ date ]</a> + <a href="thread.html#817">[ thread ]</a> + <a href="subject.html#817">[ subject ]</a> + <a href="author.html#817">[ author ]</a> + </LI> + </UL> +</body></html> |