[MUD-Dev] Re: TECH: Java ARMI
bobbymartin at hotmail.com
Wed Apr 18 15:58:54 New Zealand Standard Time 2001
> From: "Adam Martin" <amsm2 at cam.ac.uk>
>> From: "Bobby Martin" <bobbymartin at hotmail.com>
>> That said, I have developed a few java tools that could help out
>> some folks. I have a high speed, compact UDP replacement for RMI,
>> which is (almost) as easy to use as RMI.
> If you opensource it, how much effort would it be for > someone to
> convert to TCP (i.e. how insulated is it from the > transport
Well, you would have to re-implement two classes:
StandardOutgoingMessageQueue and StandardIncomingMessageQueue. All
they do is translate from an interface to the underlying transport
mechanism, so they're pretty well insulated.
Unfortunately, since I wrote the code for myself and under time
constraints, as it stands right now you would have to branch the
source. There is no mechanism for 'switching out' the transport
mechanism. One reason I'm GPLing the code is so people who might have
more time on their hands (or different needs) can submit changes to
make this more reusable.
The short answer: it would take me less than a day to do so; I would
expect it to take a competent programmer who knows how to use both UDP
and TCP in Java about two or three days, given the above information
of which two classes to modify.
Cosm Development Team
MUD-Dev mailing list
MUD-Dev at kanga.nu
More information about the MUD-Dev