Comments on: Mud standards - telnet options - not a standard yet. http://www.aardwolf.com/blog/2010/07/12/mud-standards-telnet-options-mess/ Aardwolf MUD General News and Updates. Mon, 21 May 2012 17:12:48 +0000 http://wordpress.org/?v=2.6.2 By: GMCP in Aardwolf MUD http://www.aardwolf.com/blog/2010/07/12/mud-standards-telnet-options-mess/#comment-723 GMCP in Aardwolf MUD Wed, 28 Jul 2010 01:56:39 +0000 http://www.aardwolf.com/blog/?p=285#comment-723 Check the most recent post for an update on this: http://www.aardwolf.com/blog/2010/07/27/gmcp-generic-mud-communicationprotocol/ Check the most recent post for an update on this: http://www.aardwolf.com/blog/2010/07/27/gmcp-generic-mud-communicationprotocol/

]]> By: Bremen http://www.aardwolf.com/blog/2010/07/12/mud-standards-telnet-options-mess/#comment-714 Bremen Fri, 16 Jul 2010 07:02:31 +0000 http://www.aardwolf.com/blog/?p=285#comment-714 I'd love to see more posts like this, sort of a behind-the-scenes running-the-MUD/coding blog, in that fourth 40 hours/wk of your free time. :) I’d love to see more posts like this, sort of a behind-the-scenes running-the-MUD/coding blog, in that fourth 40 hours/wk of your free time. :)

]]> By: Lasher http://www.aardwolf.com/blog/2010/07/12/mud-standards-telnet-options-mess/#comment-712 Lasher Tue, 13 Jul 2010 18:21:58 +0000 http://www.aardwolf.com/blog/?p=285#comment-712 Yeah I didn't define "bloat" very well. I am thinking in terms of "What can I quickly parse in 'C'?". By quickly, I mean CPU cycles. I can process a simple sequence terminated by IAC-SE far quicker than I can run it through a JSON parser. If the comparison were, for example, JSON vs XML, JSON would clearly win hands down. Does this matter? In terms of CPU how does parsing a JSON array compare to something we do often like displaying a room map or compressing a transmit buffer? I don't know. Like I said, I do plan to implement both so it will be interesting to find out and I do fully reserve the right to turn around in 2 weeks time and declare that I was completely wrong :) Yeah I didn’t define “bloat” very well. I am thinking in terms of “What can I quickly parse in ‘C’?”. By quickly, I mean CPU cycles. I can process a simple sequence terminated by IAC-SE far quicker than I can run it through a JSON parser. If the comparison were, for example, JSON vs XML, JSON would clearly win hands down.

Does this matter? In terms of CPU how does parsing a JSON array compare to something we do often like displaying a room map or compressing a transmit buffer? I don’t know. Like I said, I do plan to implement both so it will be interesting to find out and I do fully reserve the right to turn around in 2 weeks time and declare that I was completely wrong :)

]]> By: rathik http://www.aardwolf.com/blog/2010/07/12/mud-standards-telnet-options-mess/#comment-710 rathik Tue, 13 Jul 2010 05:28:14 +0000 http://www.aardwolf.com/blog/?p=285#comment-710 I feel like I'm missing something, as I'm sure there is some motivation to be working on this. What is wrong with the existing implementation? What was it supposed to support that it doesn't? As an author of a few scripts floating around, I haven't had much of an issue with the existing telnet negotiation, but I'd also be interested to hear what kind of new features the change would afford us. Also, this is the first time I've heard JSON and bloat mentioned together. It must be a matter of perspective. :P I feel like I’m missing something, as I’m sure there is some motivation to be working on this. What is wrong with the existing implementation? What was it supposed to support that it doesn’t?

As an author of a few scripts floating around, I haven’t had much of an issue with the existing telnet negotiation, but I’d also be interested to hear what kind of new features the change would afford us.

Also, this is the first time I’ve heard JSON and bloat mentioned together. It must be a matter of perspective. :P

]]>