I've defined an interface to be used by those components that require stream-as-file semantics, i.e. the 'jar:' protocol handler and the classic browser plug-in API. See: http://lxr.mozilla.org/seamonkey/source/netwerk/cache/public/nsIStreamAsFile.idl The cache manager already implements this interface (with some caveats - see below). In an ideal world, I think each protocol handler would be able to handle the nsIChannel::CACHE_AS_FILE flag and, via some Open, hand back an instance of nsIStreamAsFile. This would limit knowledge of whether or not a URI refers to a local file within each protocol handler. However, I don't think this will happen any time soon, so I'm proposing a subroutine that reads from a URL and stores the result in the cache. (See attachment.) I think this method should live in nsIIOService since it will be needed by multiple callers.

I said there were some caveats about the cache manager implementing nsIStreamAsFile. First, I've never tested that portion of the cache manager and it may need some debugging. Second, looking over the code, I found one problem. (Patch attached). I'll need you to check this in for me once the tree opens.

Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache component.

Depends on implementing the disk cache. Davidm says that there's code there for stream-as-file, but it's not hooked up to the protocols yet, and hasn't been tested.

This bug blocks bug 27763, which is beta1 PDT+, so I'm nominating this bug for beta1 review as well.

Note: if PDT team assigns a fix cut-off date to this bug, for consistency, it shouldn't be earlier than the fix cut-off date for bug 27763, which is beta1 PDT+.

However, as I said in bug 27763, Stanley is working on an alternative solution that doesn't involve stream-as-file.

Putting on PDT-. We really want java and hope that stanleys work if fruitful

Reassigning to davidm. Marking beta2.

reassigning

David, can you please post a status update here? Thanks,

Moving to M15.

Moving what's not done for M15 to M16.

Need to know the latest input on this...is there more needed here than protocol handler and the classic browser plug-in support? What is still the blocker for beta2?

Not needed for nsbeta2 since this is only for downloaded jar files.

This does not only affect jar file support - it's needed by legacy plugins also. See http://bugzilla.mozilla.org/show_bug.cgi?id=27763 and http://bugzilla.mozilla.org/show_bug.cgi?id=23667

You're right. Marking nsbeta2 again.

checked in code. I tested it using a version of testprotocols. If anyone knows of any code to exercise stream as file using mozilla let me know.

Don't the audio plugins do this (e.g. RealAudio)? Ask amusil or av.

The plugin glue code at http://lxr.mozilla.org/seamonkey/source/modules/plugin/nglsrc/nsPluginHostImpl.c pp doesn't use the cache yet, so you won't be able to exercise stream as file using a plugin yet.

verified