+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
On Sat, Dec 23, 2017 at 3:53 PM, Stefan Eissing
wrote:
>
> I think this really is a bug in our runtime. The flag was invented
> just for precaution, in case a module would rely on the no-copy
> behaviour. That is really close to saying: we will not fix
> any more
On Fri, Dec 22, 2017 at 6:14 PM, Stefan Eissing
wrote:
>
> The changes in h2_h2.c and h2_switch.c work find in my test. However, the
> change in h2_conn.c which sets CONN_STATE_LINGER does not. It prevents the
> last GOAWAY frame from the server to be sent out, in
> I think this really is a bug in our runtime. The flag was invented
> just for precaution, in case a module would rely on the no-copy
> behaviour. That is really close to saying: we will not fix
> any more bugs in 2.4.x as someone could rely on it.
I don't think this bit is fair. Every config
> Am 23.12.2017 um 12:34 schrieb Yann Ylavic :
>
> On Sat, Dec 23, 2017 at 9:00 AM, Nick Kew wrote:
>> On Sat, 2017-12-23 at 08:20 +0100, Stefan Eissing wrote:
>>
Ugh. Fine for trunk, but that's a lot of complexity to foist on
a stable branch.
On Sat, Dec 23, 2017 at 9:00 AM, Nick Kew wrote:
> On Sat, 2017-12-23 at 08:20 +0100, Stefan Eissing wrote:
>
>> > Ugh. Fine for trunk, but that's a lot of complexity to foist on
>> > a stable branch. A module would not only need to check MMN,
>> > but also implement fallback
On Sat, 2017-12-23 at 08:20 +0100, Stefan Eissing wrote:
> > Ugh. Fine for trunk, but that's a lot of complexity to foist on
> > a stable branch. A module would not only need to check MMN,
> > but also implement fallback behaviour if there are no flags.
> > So why not KISS and stick with that