简体   繁体   English

没有 IAC SE 的 Te.net 子协商命令

[英]Telnet sub negotiation command without IAC SE

Does te.net sub negotiation command without IAC SE is valid command?没有 IAC SE 的 te.net 子协商命令是否有效?

No, the IAC, SE sequence indicates the end of the response (and the supplied value).不,IAC、SE 序列指示响应的结尾(和提供的值)。
See Documentation请参阅 文档

Like @Robert Bradley says, a sub-option negotiation which does not end with <IAC><SE> is NOT valid.正如@Robert Bradley 所说,不以<IAC><SE>结尾的子选项协商无效。

However there is one unofficial exception, which, because it was broken like that, got replaced, but theoretically could be seen in the wild .不过有一个非官方的例外,就是因为那样坏了,被换掉了,不过理论上是可以在野外看到的 That is the original version of the M ud C lient C ompression P rotocol (MCCP - using sub-option number 85 which uses zlib compression to reduce the amount of data bytes to be sent from a MUD (Multi-User Dungeon) Game Server to the players' Clients. That mistakenly has the Server using <IAC><SB><85><WILL><SE> at the exact point in the data where compression begins. This defect was so significant that the protocol was revised to version 2 - which is otherwise identically except that it uses the sub-option number 86 instead - so that the sequence to begin that (after both server and client have agreed) is the correctly formed: <IAC><SB><86><WILL><SE> .这是M ud C lient C压缩协议的原始版本(MCCP - 使用子选项编号 85,它使用zlib压缩来减少从 MUD(多用户地牢)游戏服务器发送到玩家的客户端。错误地让服务器在压缩开始的数据中的确切位置使用<IAC><SB><85><WILL><SE> 。这个缺陷非常严重,以至于协议被修订为版本 2 - 除了它使用子选项编号 86 之外其他方面完全相同 - 因此开始的序列(在服务器和客户端都同意之后)是正确形成的: <IAC><SB><86><WILL><SE>

MUD server and client applications are now to prefer MCCP2 over MCCP1 (and obviously not agree to do the latter if the former has already been negotiated). MUD 服务器和客户端应用程序现在更喜欢 MCCP2 而不是 MCCP1(如果前者已经协商,显然不同意执行后者)。 See also: https://smaugmuds.afkmods.com/mccp/protocol.html .另请参阅: https://smaugmuds.afkmods.com/mccp/protocol.html

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM