Thread: MCCP 3
View Single Post
Old 05-06-2020, 12:20 PM   #5
Istarian
New Member
 
Join Date: May 2015
Posts: 3
Istarian is on a distinguished road
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
or
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?

P.S.

It seems you need to fix your link to the mud codebase comparisons from:

TO


Also, your mudpedia link leads gets a site unreachable error and per archive.org snapshots seems to have been dead since 2012.
Istarian is offline   Reply With Quote