Closed Bug 123203 Opened 23 years ago Closed 10 years ago

nsHttpChannel should own a nsStandardURL instead of a generic nsIURI

Categories

(Core :: Networking, defect, P4)

Product:
Core
Component:
Networking
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: darin.moz, Unassigned)

Details

(Keywords: perf)

nsHttpChannel should own a nsStandardURL instead of a generic nsIURI. this would allow nsHttpChannel to save on space my making mSpec reference nsStandardURL::mSpec directly. it would also avoid a number of other pointless buffer copies throughout the HTTP impl.
Severity: normal → minor
Status: NEW → ASSIGNED
Keywords: perf
Priority: -- → P4
Target Milestone: --- → mozilla0.9.9
-> future
Target Milestone: mozilla0.9.9 → Future
at some point my company is going to try to force http to use some other impl of nsIURI. we don't want to have to reimplement http or all of necko, we like mozilla, but this would be fairly bad for us.
-> default owner
Assignee: darin → nobody
Status: ASSIGNED → NEW
Component: Networking: HTTP → Networking
QA Contact: tever → networking
Target Milestone: Future → ---
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.