blob: e5d91059bc638a8d836db55c6e0eac24928ac3bc (
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
|
<!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:v.caron%40zerodeux.net">
<LINK REL="Previous" HREF="000297.html">
<LINK REL="Next" HREF="000301.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Nel] NeL Network Engine</H1>
<B>Vincent Caron</B>
<A HREF="mailto:v.caron%40zerodeux.net"
TITLE="[Nel] NeL Network Engine">v.caron@zerodeux.net</A><BR>
<I>Wed, 28 Feb 2001 16:30:55 +0100</I>
<P><UL>
<LI> Previous message: <A HREF="000297.html">[Nel] NeL Network Engine</A></li>
<LI> Next message: <A HREF="000301.html">[Nel] NeL Network Engine</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#298">[ date ]</a>
<a href="thread.html#298">[ thread ]</a>
<a href="subject.html#298">[ subject ]</a>
<a href="author.html#298">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>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 ...
</pre>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000297.html">[Nel] NeL Network Engine</A></li>
<LI> Next message: <A HREF="000301.html">[Nel] NeL Network Engine</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#298">[ date ]</a>
<a href="thread.html#298">[ thread ]</a>
<a href="subject.html#298">[ subject ]</a>
<a href="author.html#298">[ author ]</a>
</LI>
</UL>
</body></html>
|
