aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-February/000304.html
blob: b2474f3f5f0afde9f4557fb092f18760e6ba8b5b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
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: &quot;Vincent Caron&quot; &lt;<A HREF="mailto:v.caron@zerodeux.net">v.caron@zerodeux.net</A>&gt;
Subject: Re: [Nel] NeL Network Engine


&gt;<i> I was more or less suggesting than the solution is not a matter of
</I>adopting
&gt;<i> select() or not, but rather implies a deeper reflexion on the pb of
</I>service
&gt;<i> scheduling... And being cross-platform doesn't mean being uniform, it
</I>would
&gt;<i> be a shame to ignore each OS's specificity. An approach could be to get
</I>the
&gt;<i> best implementation, say, for Linux and Windows, find out an abstract
</I>model
&gt;<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>