Developing the IO architecture of an internal server

[forkgenesis]

This discussion is dedicated to the main feature of this mod/plugin - the internal server. It opens and closes with every Minecraft server that has this mod installed. I'm choosing an input/output architecture (IO for short). This discussion is about choosing and - you guessed it - developing it.

The internal server is a TCP-server, and every connection between it and a TCP-client is a socket. Every socket should open for a single request-response exchange. That's my main goals for this technology. Now it's time to pick the most modern and efficient way of doing so.

Options

• Basic multithreaded socket server: A thread is opened alongside Minecraft's own thread to handle the server itself and accepting clients, and each time a client is accepted, a new thread opens to handle its socket.
• Java.NIO async socket server: A thread is opened alongside Minecraft's own thread to handle the server itself and all of the client connections simultaneously (asynchronously).
• Java.NIO async & multithreaded socket server: A thread is opened alongside Minecraft's own thread to handle the server itself and a limited number of threads are opened alongside it to handle client connections, asynchronously in each thread.

[forkgenesis]

Forgot to add that this is also a discussion on the best I/O library that you can suggest.

[forkgenesis]

As of time of writing this, I'm sticking to Java IO basic multithreaded server.

[forkgenesis]

It's so cringe I don't understand anything RAAAHHH

[forkgenesis]

There are 2 ways to handle a connection. 1) To create a connection (and a thread, in my case) for each single request-response, 2) To create a connection for each client.
So, I wrote a server and a client (both on Java) that endlessly talk to see, which of the architectures is faster.

The 1st architecture runs at 1256 responses per second. The 2nd runs at 2330. We have a clean winner!!!!
Still, I need to develop this on Python too, for God's sake...

[forkgenesis]

I've developed my first multithreaded TCP server that doesn't die at the first minute of using it! 13f5a02

I use a simplified UDP-style message format:

13f5a02 13f5a02 13f5a02 13f5a02 13f5a02

[forkgenesis]

Okay, I've decided to stop talking about the mod development process here. We'll see the future of this tab.