mudlet-makers team mailing list archive

[Chris Wright <dhasenan@xxxxxxxxx>]

Urk, I mistyped a couple of constants, leading to behavior that confused
me.

The only thing I see that's wrong is that Mudlet seems to be sending
GMCP messages before negotiating to enable GMCP.

** Changed in: mudlet
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1508991

Title:
  Mudlet responds to IAC DONT GMCP with IAC WILL GMCP -- forever

Status in Mudlet:
  Invalid

Bug description:
  Mudlet 2.1, Ubuntu 14.04

  Mudlet tries to enable GMCP as the first thing it does on connecting.
  Fair enough.

  When the server says it doesn't doesn't support GMCP, Mudlet
  immediately responds by asking to enable GMCP. A polite client would
  take a hint at the first rejection and respond IAC WONT GMCP --
  agreeing with the server not to use it.

  A naively implemented server will respond to each request, resulting
  in an infinite loop of messages back and forth. That's just unkind.

  A well implemented server will have to take into account poorly
  implemented clients and reserve in memory a series of flags telling it
  that it's already negotiated for this option and not to do it again,
  expending on-machine resources to save bandwidth chatting to a client
  that won't take a bloody hint.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1508991/+subscriptions