Thanks for the replies. I think I'm confused about some of the terms here. In my reading I  see a lot about asynchronous operations (like those supported by NIO2). I always equated this with the classic multiplexed single-threaded server design (like you see in a lot of old muds that use select() and so on).

However now it seems like async and single-threaded multi-plexed are two different things. Can anyone comment as to why an async design might or might not be better for a mud?

hi,

I'm figuring out how to write a mud, and Netty sounded like a good library. However in reading about that I learned of NIO2 (new with Java 7). There are some articles out there about NIO2 but I'm wondering if anyone here has some thoughts or experience on using NIO2 vs. Netty (or similar single-threaded async libraries).

Of course NIO is an option but since I'm using Java 7 already I thought why not NIO2.

There was this thread here, http://www.java-gaming.org/topics/java-nio-unblocking-server-with-multiple-clients/20630/msg/167616/view.html#msg167616 , but it is from a few years ago so maybe there are some fresh perspectives.

Thanks for any help.

The OPer might want to read up on stuff here,

http://www.koonsolo.com/news/dewitters-gameloop/

It explains things well IMO.

hi, I'm looking for some direction to learn about hosting other languages from Java. So far I've found things like JSR 223 and the Bean Scripting Framework but I don't have any idea what is a good idea, active, and so forth.

The application is a mud where the game systems are run as services that connect (via a socket) to a core server. I'm using this approach so developers can write the game systems in any language.

However a developer (or me) still has to write client/server code to connect to my core server. Ideally I would like my mud to take care of this step, so I was thinking of writing a small networking module that could load code from any language, or at least a number of popular languages.