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
There are several identified places where the Talker outputs raw information to their clients:
motd
.map
.file
A filter must be created, catching these streams and turning them into a line-by-line output to send to the client, letting the client be the one handling with termination lines and whatnot. This will solve the output of these commands to Windows' telnet client.
Sure. In some parts (at least the three identified in the description), TalkerNode reads something that might have multiple lines (from a file, for example), and sends it to a client's socket. The problem with this approach is that "new lines" aren't parsed, and different clients will end up showing different things (notably, with differences between DOS and Unix systems: https://www.cs.toronto.edu/~krueger/csc209h/tut/line-endings.html). To solve this, a new parser can be created, and in those three places, instead of sending the multiline data to the socket, we can call that new function with the data and socket as a parameter, and the function will read the data and send it to the socket line by line).
There are several identified places where the Talker outputs raw information to their clients:
A filter must be created, catching these streams and turning them into a line-by-line output to send to the client, letting the client be the one handling with termination lines and whatnot. This will solve the output of these commands to Windows' telnet client.
This was first identified in #121 (comment) .
The text was updated successfully, but these errors were encountered: