Optimize closing transaction in nsHttpChannel::ReadFromCache when cache wins the race

NEW
Unassigned

Status

()

P3
normal
a year ago
a year ago

People

(Reporter: michal.novotny, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-backlog])

(Reporter)

Description

a year ago
From bug 1367742 comment 26:
> For a followup bug: the proper way for h1 (whether h1/2 should be hidden
> from nshttpchannel) is to let the transaction finish and just discard the
> data.  This is the idea of 'soft closing' a transaction.  To be even more
> perfectionist the transaction should be hard-canceled when the remaining
> amount of data is too large and would just waste bandwidth.  The threshold
> is hard to figure out, so definitely not something to be done for 57 or 58,
> but definitely something to be filed at least.
You need to log in before you can comment on or make changes to this bug.