mudlet-makers team mailing list archive
-
mudlet-makers team
-
Mailing list archive
-
Message #01967
Re: [Bug 906743] [NEW] Output parsing freezes after receiving Z_STREAM_END
Hi,
the problem is that the MCCP protocol does not cover server controlled
termination of the zstream.
The standard procedure is to disconnect all connections on reboot.
Which MUD do you run (server + port please)?
I'll commit the patch, but I may need to run a few tests on your server.
Heiko
Am 20.12.11 07:38, schrieb mitchej123:
> Public bug reported:
>
> 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.
>
> ** Affects: mudlet
> Importance: Undecided
> Status: New
>
--
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
References