mudlet-makers team mailing list archive

[mitchej123 <906743@xxxxxxxxxxxxxxxxxx>]

** Patch added: "Properly handle Z_STREAM_END, allowing for output to continue after ending compression, and allow for renegotation of MCCP (after a copyover for example)"
   https://bugs.launchpad.net/bugs/906743/+attachment/2640813/+files/mccp.patch

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

Title:
  Output parsing freezes after receiving Z_STREAM_END

Status in Mudlet the MUD client:
  New

Bug description:
  Upon receiving Z_STREAM_END mudlet stops handling output from the mud
  server.  Upon looking at the code it looks like it correctly calls
  inflateEnd, however it doesn't reset any of the compression options so
  the client is still looking for compressed data and never gets any.

  I noticed this issue when one of my users complained that her
  mudclient [mudlet] froze on reboot(copyover).  My mud server first
  ends compression, reboots, and then attempts to re-negotiate it.

  I've attached a patch that seems to address the issue.

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