diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-February/000298.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-February/000298.html')
| -rw-r--r-- | pipermail/nel/2001-February/000298.html | 51 |
1 files changed, 51 insertions, 0 deletions
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 @@ +<!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> |