Open
Bug 1528283
Opened 6 years ago
Updated 2 years ago
Consider on-demand data coalescing by nsHttpTransaction
Categories
(Core :: Networking: HTTP, enhancement, P3)
Core
Networking: HTTP
Tracking
()
NEW
People
(Reporter: mayhemer, Unassigned)
Details
(Whiteboard: [necko-triaged])
Some consumers, like js and css loaders, don't do at the moment incremental parsing and only collect the data to be parsed as a final blob in onstoprequest. Some servers are sending data in very small chunks (kB) possibly leading to overhead from messaging chains each chunk invokes.
The idea is to have an API on nsIHttpChannel(Internal) to call before AsyncOpen taking number of bytes to coalesce by. Data would then be buffered in lower network levels, flushed on overreaching the limit or when onstoprequest fires.
This is experimental only.
Updated•6 years ago
|
Whiteboard: [necko-triaged]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•