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