[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

6654: [MUD-Dev] Re: OT: Java multithreading performance

[Full Header] [Plain Text]
From: "Chris Gray" <cg@ami-cg.GraySage.Edmonton.AB.CA>
Newsgroups: nu.kanga.list.mud-dev
Date: Tue, 19 May 98 22:29:22 MST
Organization: Kanga.Nu
[Ben Greear:]

:The socket limit has me worried.  I can't think of a clean way to get
:around this in Java.  I suppose I could do a 
:
:System.??("java AnotherServerBackEnd")
:
: but that seems messy at best.
:Anyone got around this, or know of a project which has tried?

It's expensive, but you could use extra processes, whose sole purpose is
to have lots of sockets open. They would then forward the message, tagged
as to who it came from, to the main server socket[s]. The server could
write all data to a single connectionless socket, or forward it through
the extra processes.

--
Chris Gray   cg@ami-cg.GraySage.Edmonton.AB.CA


--
MUD-Dev: Advancing an unrealised future.