You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to consider replacing game-server-base with a more reliable alternative in the future. Game-server-base effectively holds us back, limiting the versions of our dependencies and in the end even introducing security issues through that.
I'd thus consider writing our own telnet server implementation using telnetlib3 (https://telnetlib3.readthedocs.org/), which is rather up-to-date and supports many of the standard default functions, which might allow us more functionalities in the future, like sending data outside of the standard output stream (MSP, MCCP etc) if needed. All the clients currently using our MUD are already MUD clients and thus support the telnet protocol.
Any alternatives which need to be evaluated here? That should be an evaluation ticket, which in the first place should allow us to get an overview of the available tools and the workflow that we'll need to follow when introducing a new server framework. @tspivey: any experiences that might help us here?
The text was updated successfully, but these errors were encountered:
I'd like to consider replacing game-server-base with a more reliable alternative in the future. Game-server-base effectively holds us back, limiting the versions of our dependencies and in the end even introducing security issues through that.
I'd thus consider writing our own telnet server implementation using telnetlib3 (https://telnetlib3.readthedocs.org/), which is rather up-to-date and supports many of the standard default functions, which might allow us more functionalities in the future, like sending data outside of the standard output stream (MSP, MCCP etc) if needed. All the clients currently using our MUD are already MUD clients and thus support the telnet protocol.
Any alternatives which need to be evaluated here? That should be an evaluation ticket, which in the first place should allow us to get an overview of the available tools and the workflow that we'll need to follow when introducing a new server framework.
@tspivey: any experiences that might help us here?
The text was updated successfully, but these errors were encountered: