UOX3.org

Ok, so as I continue to work on UOX (my c++17 project), I have decided on the following use of threads:
1 thread for the relays server - I have decided this is a low priority thing, so it is done sequentially, and in a single thread.
1 thread for the game server - This then uses a thread pool to server and work on items.
1 thread for the console - if I do a console. This is a tad different then uox3, but more on that later.

I finally decided to do a relay server and game server, because I finally decided that really is the correct way (imho). The advantage, is if I wanted to , I could do the relay server as a stand alone on some other ip. The downside, is one has to open two ports in their router if behind one.

In this day and age, I'd probably consider a set of REST APIs over the top of the server rather than a console.

Then you can build whatever sort of maintenance/review process you want (even a console) which you can maintain as a separate component

I think we basically are saying the same thing, just perhaps a different implementation. I do believe the console is a module that has a defined interface to the rest of the system. So in that light, I think its is the same. I understand that the world has migrated to web based items, and restapi being a well constructed url for an application to act on is a natural extension. But I don't see that it really offers anything more over any other defined api, unless I was going to be web based solution.