aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-February/000301.html
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--pipermail/nel/2001-February/000301.html74
1 files changed, 74 insertions, 0 deletions
diff --git a/pipermail/nel/2001-February/000301.html b/pipermail/nel/2001-February/000301.html
new file mode 100644
index 00000000..57cabbb7
--- /dev/null
+++ b/pipermail/nel/2001-February/000301.html
@@ -0,0 +1,74 @@
+<!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:cblt%40cblt.org">
+ <LINK REL="Previous" HREF="000298.html">
+ <LINK REL="Next" HREF="000304.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Nel] NeL Network Engine</H1>
+ <B>Nicolas Hognon</B>
+ <A HREF="mailto:cblt%40cblt.org"
+ TITLE="[Nel] NeL Network Engine">cblt@cblt.org</A><BR>
+ <I>Wed, 28 Feb 2001 16:11:22 +0100</I>
+ <P><UL>
+ <LI> Previous message: <A HREF="000298.html">[Nel] NeL Network Engine</A></li>
+ <LI> Next message: <A HREF="000304.html">[Nel] NeL Network Engine</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#301">[ date ]</a>
+ <a href="thread.html#301">[ thread ]</a>
+ <a href="subject.html#301">[ subject ]</a>
+ <a href="author.html#301">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>i'm aggry with you
+at this time i'll use select for windows and linux (or poll for linux)
+and design my server so that i can implement another better solution.
+
+has i said before better solution under windows are
+ - are windows message and event and i don't want use it
+ - overlapped I/O but i don't really understand how it works
+ so it's not easy to design a server which is able to use select and this
+ technic. perhaps you already know it but you can take a look at
+<A HREF="http://www.cyberport.com/~tangent/programming/winsock/articles/io-strategies.html">http://www.cyberport.com/~tangent/programming/winsock/articles/io-strategies.html</A>
+
+
+&gt;<i> I was more or less suggesting than the solution is not a matter of adopting
+</I>&gt;<i> select() or not, but rather implies a deeper reflexion on the pb of service
+</I>&gt;<i> scheduling... And being cross-platform doesn't mean being uniform, it would
+</I>&gt;<i> be a shame to ignore each OS's specificity. An approach could be to get the
+</I>&gt;<i> best implementation, say, for Linux and Windows, find out an abstract model
+</I>&gt;<i> that unifies both and brings this into NeL. Here again, just a hint ...
+</I>
+
+
+--
+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="000298.html">[Nel] NeL Network Engine</A></li>
+ <LI> Next message: <A HREF="000304.html">[Nel] NeL Network Engine</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#301">[ date ]</a>
+ <a href="thread.html#301">[ thread ]</a>
+ <a href="subject.html#301">[ subject ]</a>
+ <a href="author.html#301">[ author ]</a>
+ </LI>
+ </UL>
+</body></html>