TWX Telnet code cleanup

7 views
Skip to first unread message

EP

unread,
Aug 26, 2008, 2:03:03 PM8/26/08
to TWXProxy
In eliminating TWX's dependancy on external libraries, I hacked the
server telnet code for use on the client side. I'm going to be
working on getting this cleaned up, hopefully unifying the telnet
handling code for the server and client sides. And while I'm there,
I'll add the initial handling of HIPS messages in the telnet stream.

Don Brown

unread,
Aug 27, 2008, 8:59:15 AM8/27/08
to twxp...@googlegroups.com
Cool, getting HIPS support for incoming messages is really the blocker
for the web client right now. Just be sure they aren't parsed if it
isn't enabled globally.

Don

EP

unread,
Sep 9, 2008, 4:09:06 PM9/9/08
to TWXProxy
I've figured out how I'm going to restructure the telnet code. Free
time has been scarce though.

The implementation of the twx client telnet processor that is in the
current source doesn't maintain a list of negotiated options on a
connection by connection basis. This will be irrelevant for the
server side proxy, but will be important to get right for the next
public release of twx, and for handling telnet on the server and
client side with the same telnet processor.

The logical place for parsing the HIPS messages is in the ANSI
processor, since these are in the form of ANSI escape sequences. The
ANSI processor is simpler too, so it makes more sense to do it there.
I'm aiming to have these done in the next week.

Patrick
Reply all
Reply to author
Forward
0 new messages