Closed Bug 42772 Opened 24 years ago Closed 20 years ago

eliminate StreamIO::Open

Categories

(Core :: Networking, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED INVALID
Future

People

(Reporter: jud, Assigned: dougt)

Details

(Keywords: arch)

api and functionality cleanup.
Keywords: arch
Target Milestone: --- → M18
Here's the idea here: nsIFileIO is the logical extension if nsIFile that
provides access to input/output streams onto a file. It is itself a
specialization of nsIStreamIO -- a generic interface that provides access to
streams that doesn't know per se that it is talking to files at the other end.

What we (I) would like to do here is move nsIStreamIO, nsIFileIO,
nsIFileInputStream, nsIFileOutputStream, nsIBufferedInputStream and
nsIBufferedOutputStream all to xpcom/io (where they logically belong). The only
thing stopping us is that nsIStreamIO::Open returns a content type (mime type),
and that mechanism for determining the content type is part of necko.

We should probably find some other interface to hang a GetContentType method off
of. Xpcom would like to have file i/o operations so that people don't have to
resort to low-level nspr stuff.
Warren, I am reassigning some bugs which you own over to me (dougt).  If you 
think that you will have time to address them please reassign them back to 
yourself.  This reassignment was suggested by choffman.
Assignee: warsome → dougt
unsetting milestone.  Won't get it this for a while.
Target Milestone: M18 → ---
Target Milestone: --- → Future
mass move, v2.
qa to me.
QA Contact: tever → benc
API Changes.
Target Milestone: Future → mozilla1.0
Keywords: mozilla1.0
I do not believe this is part of the mozilla 1.0 API freeze.  
Target Milestone: mozilla1.0 → Future
agreed.
marking INVALID since nsIStreamIO and nsIFileIO no longer exist.

moving file streams and buffered streams into xpcom/io still makes good sense to
me, but we'll leave to another bug.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
V/invalid.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.