From 0ea5fc66924303d1bf73ba283a383e2aadee02f2 Mon Sep 17 00:00:00 2001 From: neodarz Date: Sat, 11 Aug 2018 20:21:34 +0200 Subject: Initial commit --- pipermail/nel/2001-February/000298.html | 51 +++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) create mode 100644 pipermail/nel/2001-February/000298.html (limited to 'pipermail/nel/2001-February/000298.html') diff --git a/pipermail/nel/2001-February/000298.html b/pipermail/nel/2001-February/000298.html new file mode 100644 index 00000000..e5d91059 --- /dev/null +++ b/pipermail/nel/2001-February/000298.html @@ -0,0 +1,51 @@ + + + + [Nel] NeL Network Engine + + + + + + +

[Nel] NeL Network Engine

+ Vincent Caron + v.caron@zerodeux.net
+ Wed, 28 Feb 2001 16:30:55 +0100 +

+
+ +
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 ...
+
+
+ + + +
+

+ -- cgit v1.2.1