|08-12-2019, 03:55 PM||#1|
Join Date: Jun 2004
I'd like to announce the MCCP3 protocol which I created mostly for my own purposes and I figured it might be of use to others. While MCCP2 compresses data sent from the server to the client MCCP3 compresses data sent from the client to the server.
MCCP2 uses telnet code 86, MCCP3 uses telnet code 87.
MCCP2 and MCCP3 are both described on this protocol page:
Client MCCP3 support has been added to TinTin++ 2.01.8 which runs on Windows, Linux, OS X, and Android.
Server MCCP3 support has been added to MTH which can also run stand alone in case someone needs to debug server side MCCP3 support.
While compression ratios aren't very impressive for the typical MUD server's use case, MCCP3 adds a little bit of security through obscurity by no longer sending passwords and messages as plain text.
|05-06-2020, 12:20 PM||#5|
Join Date: May 2015
Re: MCCP 3
I feel like this is rather confusing on a conceptual level.
If MCCP stands for 'Mud Client Compression Protocol' then doesn't MCCP1/2 being only the server compressing data conflict with the naming? I mean I guess it could be interpreted as compressing the output of a MUD FOR the client...
Separately, is MCCP3 then an extension of MCCP2 that compresses both the Server=>Client and Client=>Server communications or a separate protocol that only handles the latter?
I think if it's a completely separate protocol, then it really should have a different name because versioning "rules" imply that it's an updated version of the same protocol. And with that kind of implication it would make sense to start with MCCP2 and "upgrade" to MCCP3 if supported as opposed to separately enabling them.
It would make more logical sense to call them...
MCCP - Mud (to) Client Compression Protocol
CMCP - Client (to) Mud Compression Protocol
MCCP - Mud Compression (for) Clients Protocol
CCMP - Client Compression (for) MUDs Protocol
What other rationale is there for this besides a kind of security through obscurity?
It seems you need to fix your link to the mud codebase comparisons from:
Also, your mudpedia link leads gets a site unreachable error and per archive.org snapshots seems to have been dead since 2012.