From 0ea5fc66924303d1bf73ba283a383e2aadee02f2 Mon Sep 17 00:00:00 2001 From: neodarz Date: Sat, 11 Aug 2018 20:21:34 +0200 Subject: Initial commit --- pipermail/nel/2001-February/000304.html | 73 +++++++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) create mode 100644 pipermail/nel/2001-February/000304.html (limited to 'pipermail/nel/2001-February/000304.html') diff --git a/pipermail/nel/2001-February/000304.html b/pipermail/nel/2001-February/000304.html new file mode 100644 index 00000000..b2474f3f --- /dev/null +++ b/pipermail/nel/2001-February/000304.html @@ -0,0 +1,73 @@ + + + + [Nel] NeL Network Engine + + + + + + +

[Nel] NeL Network Engine

+ Zane + zane@supernova.org
+ Wed, 28 Feb 2001 09:04:59 -0800 +

+
+ +
----- Original Message -----
+From: "Vincent Caron" <v.caron@zerodeux.net>
+Subject: Re: [Nel] NeL Network Engine
+
+
+> I was more or less suggesting than the solution is not a matter of
+adopting
+> select() or not, but rather implies a deeper reflexion on the pb of
+service
+> scheduling... And being cross-platform doesn't mean being uniform, it
+would
+> be a shame to ignore each OS's specificity. An approach could be to get
+the
+> best implementation, say, for Linux and Windows, find out an abstract
+model
+> that unifies both and brings this into NeL. Here again, just a hint ...
+
+
+Would not the wisest choice be to research all the high performance web
+servers out there?  It seems to me that this problem has been researched
+quite extensively by a LOT of other GPL projects.  I doubt you'd be able to
+find a better solution than what Apache or other heavy duty web servers have
+already implemented.
+
+-E.J. Wilburn
+zane@supernova.org
+
+
+
+
+ + + +
+

+ -- cgit v1.2.1