Open Bug 1364151 Opened 8 years ago Updated 2 years ago

Support Creating a JARChannel From a FileDescriptor or InputStream

Categories

(Core :: Networking: JAR, enhancement, P3)

55 Branch
enhancement

Tracking

()

People

(Reporter: haik, Unassigned)

References

Details

(Whiteboard: [necko-backlog])

For bug 1334550 "Proxy moz-extension protocol requests to the parent process", the parent process sends a file descriptor for a JAR file to the child so that the child can resolve moz-extension URI's to resources within the JAR file. The current approach uses a bare-bones nsIFile implementation that supports being instantiated from a file descriptor. That nsIFile is then sideloaded into a nsJARChannel. It would be simpler/cleaner if we could create a JAR channel backed by a file descriptor so that we wouldn't have to use the nsIFile implementation.
Whiteboard: [necko-backlog]
Priority: -- → P1
Priority: P1 → P3
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.