 |
Rorso
Wizard
Joined: 14 Oct 2000
Posts: 1368
|
 Posted: Wed Jul 16, 2008 4:38 pm
[2.31] Nonstandard MXP version 1.1
|
I just noticed that cMUD use a new version of MXP, the 1.1 version. The official protocol might need to be updated to include the new information and get its version number increased.
http://www.zuggsoft.com/zmud/mxp.htm
Edit: I got to start read :-P. Well seems I found the 2.31 version on the changes document before the version had actually been released :p.
Zugg could old versions of the MXP protocol be stored as well? Say you have one current official version, and one working version. A bit like beta protocol, and then when it seem stable it is set as new official version. For compatibility reasons it might be interesting to store all previous official versions of the protocol as well. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Jul 16, 2008 8:54 pm
|
Well, the 1.1 version isn't really that different from 1.0. In fact, it's not really a "protocol" change per-se, so maybe I shouldn't have done it this way.
But I wanted there to be an easy way for servers to detect the newer MXP with all of the FRAME bug fixes, as well as the new arguments like DOCK in the frame command. But since FRAME is an optional tag for MXP, it doesn't really effect the main protocol.
Most of these changes can be detected via the SUPPORTS tag. But when I also fixed the problem with not recognizing character and % width/height arguments, I realized that couldn't be detected with SUPPORTS. And since zMUD also had this problem with character and % arguments, I decided to bump the MXP version to make it easier on server developers who are using these new features.
I never want to change the MXP spec in any way that makes it incompatible with older specs. So I just plan to indicate changes within the document. For example, in the FRAME section, it will just say that DOCK was added in the 1.1 spec.
When we start working on additional enhancements, like the mapper stuff, I will probably put that into a separate document from the main MXP spec since what we will really be doing is defining additional "optional" MXP tags rather than making any changes to the base MXP protocol. |
|
|
|
|
Rorso
Wizard
Joined: 14 Oct 2000
Posts: 1368
|
Posted: Wed Jul 16, 2008 10:20 pm
|
| Zugg wrote: |
Most of these changes can be detected via the SUPPORTS tag. But when I also fixed the problem with not recognizing character and % width/height arguments, I realized that couldn't be detected with SUPPORTS. And since zMUD also had this problem with character and % arguments, I decided to bump the MXP version to make it easier on server developers who are using these new features.
|
The server could check the clientversion using the version tag though:
<VERSION MXP=mxpversion STYLE=styleversion CLIENT=clientname VERSION=clientversion REGISTERED=yes/no>
It could still report correct MXP version, and yet another client version. So to detect bugfixed version they could check clientname & clientversion and see if that match. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Jul 16, 2008 10:22 pm
|
Yep, I thought about that. I was just trying to make it a bit easier so the MUD didn't need to know exactly which version of CMUD fixed these issues.
As I said, it probably wasn't the best way to do it, but oh well. |
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
