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-February/000304.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-February/000304.html')
| -rw-r--r-- | pipermail/nel/2001-February/000304.html | 73 |
1 files changed, 73 insertions, 0 deletions
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 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] NeL Network Engine</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:zane%40supernova.org"> + <LINK REL="Previous" HREF="000301.html"> + <LINK REL="Next" HREF="000305.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] NeL Network Engine</H1> + <B>Zane</B> + <A HREF="mailto:zane%40supernova.org" + TITLE="[Nel] NeL Network Engine">zane@supernova.org</A><BR> + <I>Wed, 28 Feb 2001 09:04:59 -0800</I> + <P><UL> + <LI> Previous message: <A HREF="000301.html">[Nel] NeL Network Engine</A></li> + <LI> Next message: <A HREF="000305.html">[Nel] NeL Network Engine</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#304">[ date ]</a> + <a href="thread.html#304">[ thread ]</a> + <a href="subject.html#304">[ subject ]</a> + <a href="author.html#304">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>----- Original Message ----- +From: "Vincent Caron" <<A HREF="mailto:v.caron@zerodeux.net">v.caron@zerodeux.net</A>> +Subject: Re: [Nel] NeL Network Engine + + +><i> I was more or less suggesting than the solution is not a matter of +</I>adopting +><i> select() or not, but rather implies a deeper reflexion on the pb of +</I>service +><i> scheduling... And being cross-platform doesn't mean being uniform, it +</I>would +><i> be a shame to ignore each OS's specificity. An approach could be to get +</I>the +><i> best implementation, say, for Linux and Windows, find out an abstract +</I>model +><i> that unifies both and brings this into NeL. Here again, just a hint ... +</I> + +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 +<A HREF="mailto:zane@supernova.org">zane@supernova.org</A> + + + +</pre> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000301.html">[Nel] NeL Network Engine</A></li> + <LI> Next message: <A HREF="000305.html">[Nel] NeL Network Engine</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#304">[ date ]</a> + <a href="thread.html#304">[ thread ]</a> + <a href="subject.html#304">[ subject ]</a> + <a href="author.html#304">[ author ]</a> + </LI> + </UL> +</body></html> |