Closed Bug 4707 Opened 26 years ago Closed 25 years ago

Need to be able to access contents of archives

Categories

(Core :: Networking, defect, P3)

x86
Other
defect

Tracking

()

VERIFIED DUPLICATE of bug 12579

People

(Reporter: hyatt, Assigned: jud)

Details

I need to be able (through a resource URL) to refer to files within a named JAR archive. I have no idea what the syntax will be for this, but a comment in nsNetService.cpp implies that you plan on adding support for accessing JARs through resource URLs at the very least. This is a requirement for downloadable chrome, to be able to give a URL that specifies a JAR and a file within the JAR and to be able to have that read in.
Assignee: gagan → dveditz
Target Milestone: M5
Maybe dan (xpinstall) folks are working on this.
Dan/Cathleen, can you set the target milestone for this?
Assignee: dveditz → valeski
Target Milestone: M5 → M6
I set the target milestone to M6 arbitrarily (it's not M5). E-mail from valeski implies he's working on the URL access so I'll reassign
Target Milestone: M6 → M8
->m8. I think this is when this might be landing as part of necko p2
Target Milestone: M8 → M9
Changing all Networking Library/Browser bugs to Networking-Core component for Browser. Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do this in a bulk change. If this happens, I will fix. ;-)
Status: NEW → ASSIGNED
Target Milestone: M9 → M10
haven't even started. moving to M10. our old libjar lib has been xpcomified. now we just need to define the url syntax for jar files, and how resource urls map to jar urls.
I will be very excited once this is online, since we should see a nice performance speedup from moving all our chrome files into jar bundles.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 12579 ***
Bulk move of all Networking-Core (to be deleted component) bugs to new Networking component.
Status: RESOLVED → VERIFIED
verified duplicate of bug 12579. 12579 covers the jar: protocol.
You need to log in before you can comment on or make changes to this bug.