blob: ee0d6fa55d9fe64aebedf8b4568ab69b98e72bf2 (
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
|
<!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:elw%40stderr.org">
<LINK REL="Previous" HREF="000305.html">
<LINK REL="Next" HREF="000307.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Nel] NeL Network Engine</H1>
<B>elijah wright</B>
<A HREF="mailto:elw%40stderr.org"
TITLE="[Nel] NeL Network Engine">elw@stderr.org</A><BR>
<I>Wed, 28 Feb 2001 13:51:45 -0500 (EST)</I>
<P><UL>
<LI> Previous message: <A HREF="000305.html">[Nel] NeL Network Engine</A></li>
<LI> Next message: <A HREF="000307.html">[Nel] NeL Network Engine</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#306">[ date ]</a>
<a href="thread.html#306">[ thread ]</a>
<a href="subject.html#306">[ subject ]</a>
<a href="author.html#306">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>><i> but the design of a web server or a ftpserver is another
</I>><i> thing than the design of a server for a MMORPG.
</I>><i> you're client is always connected to the server
</I>><i> it's not exactly the same things.
</I>
as i recall, the jabber.org people have done some scalability work for
just this kind of thing- their IM client is an always-on/always-available
service.
might be fun to ask some of them what their ideas on this are.
elijah
</pre>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000305.html">[Nel] NeL Network Engine</A></li>
<LI> Next message: <A HREF="000307.html">[Nel] NeL Network Engine</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#306">[ date ]</a>
<a href="thread.html#306">[ thread ]</a>
<a href="subject.html#306">[ subject ]</a>
<a href="author.html#306">[ author ]</a>
</LI>
</UL>
</body></html>
|
