Please check out New Worlds !

Member Discussions

terms



[Previous] [Next] [Post] [Reply] [Topics] [Summary] [Search]


1. Custom Telnet Client Wed May 4, 2005 [6:03 PM]
Scorpy
Email not supplied
member since: Jan 11, 2003
Reply
I was wondering how you could make the MUD able to identify a custom client? So you the MUD can recognise the client im specially writing for the MUD.
Imperium et Respectus
Scorpion-ice


2. RE: Custom Telnet Client Wed May 4, 2005 [6:54 PM]
eiz
eiz@codealchemy.org
member since: Dec 24, 2002
In Reply To
Reply
Well first you should implement a telnet server. Ideally this would be at least not completely half-assed. I have some code that does this if you know C# and need example code. Unfortunately the forum seems to be stripping the link so:

http://64.132.255.11/~eiz/aetascs/trunk/UfxLib/Net/Telnet/TelnetClient.cs

Now, beyond this you should implement the TTYPE telnet option to specify what kind of terminal is being used. This is documented in RFC 1091. A client should be able to return as many TTYPEs as are relevant for the terminal.

Some people like to implement their own custom, unregistered and undocumented telnet options, as well. If you're going to do this, make sure you're extra careful about picking an option number that nobody else has used for their own undocumented, unregistered telnet option.

(Comment added by eiz on Wed May 4 19:57:30 2005)

BTW, the above code needs to be refactored -- ignore the charmode stuff and the buffering. It's nasty.


3. RE: Custom Telnet Client Fri May 6, 2005 [10:57 AM]
Tharn
Email not supplied
member since: Aug 31, 2002
In Reply To
Reply
Luckly the TERMTYPE request is a properly defined procedure, so unregistered telnet options shouldn't be a problem for making a terminal type request. Good luck.




[Previous] [Next] [Post] [Reply] [Topics] [Summary] [Search]