aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-February/000280.html
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--pipermail/nel/2001-February/000280.html96
1 files changed, 96 insertions, 0 deletions
diff --git a/pipermail/nel/2001-February/000280.html b/pipermail/nel/2001-February/000280.html
new file mode 100644
index 00000000..d99dd3a6
--- /dev/null
+++ b/pipermail/nel/2001-February/000280.html
@@ -0,0 +1,96 @@
+<!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:nevrax%40holsman.net">
+ <LINK REL="Previous" HREF="000276.html">
+ <LINK REL="Next" HREF="000282.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Nel] NeL Network Engine</H1>
+ <B>Ian Holsman</B>
+ <A HREF="mailto:nevrax%40holsman.net"
+ TITLE="[Nel] NeL Network Engine">nevrax@holsman.net</A><BR>
+ <I>Mon, 26 Feb 2001 12:54:15 -0800</I>
+ <P><UL>
+ <LI> Previous message: <A HREF="000276.html">[Nel] Some screen shots</A></li>
+ <LI> Next message: <A HREF="000282.html">[Nel] Cyberspace in the 21st Century:
+ Cyberspace in the 21st Century:
+ Cyberspace in the 21st Century:
+ Cyberspace in the 21st Century : Scalability With a Big 'S'</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#280">[ date ]</a>
+ <a href="thread.html#280">[ thread ]</a>
+ <a href="subject.html#280">[ subject ]</a>
+ <a href="author.html#280">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 26 Feb 2001, you wrote in games.nevrax:
+
+ &gt;Bernard Hugueney wrote:
+ &gt;
+ &gt;I guess we're raising the question of time sharing (or 'multiplexing',
+ &gt;sounds cool :)). You can let the OS do it for you and use threads
+ &gt;everywhere : BeOS is a good example since everything than can receive
+ &gt;events is in a thread. You can do it all by yourself : use one process
+ &gt;and dispatch the incoming events to functions (ie. WinProc). Why you
+ &gt;would use one more than the other is a matter of design, and also
+ &gt;depends on the type of application and the OS you use. The anwser is
+ &gt;really not simple and won't certainly fit in a mail, but I must admit I
+ &gt;don't have good pointers to give ...
+
+for discussions on different threading models you really should be
+looking at, and drill down to the documents/technical papers.
+you probably don't want to maintain a thread per connected user, but
+have some kind of 'state' information which can be refered to by the
+incoming request.
+
+
+<A HREF="http://www.cs.wustl.edu/~schmidt/ACE.html">http://www.cs.wustl.edu/~schmidt/ACE.html</A>
+
+..Ian
+
+
+</pre>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI> Previous message: <A HREF="000276.html">[Nel] Some screen shots</A></li>
+ <LI> Next message: <A HREF="000282.html">[Nel] Cyberspace in the 21st Century:
+ Cyberspace in the 21st Century:
+ Cyberspace in the 21st Century:
+ Cyberspace in the 21st Century : Scalability With a Big 'S'</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#280">[ date ]</a>
+ <a href="thread.html#280">[ thread ]</a>
+ <a href="subject.html#280">[ subject ]</a>
+ <a href="author.html#280">[ author ]</a>
+ </LI>
+ </UL>
+</body></html>