Closed
Bug 19233
Opened 25 years ago
Closed 25 years ago
factor buffering into separate stream class
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
VERIFIED
FIXED
M14
People
(Reporter: warrensomebody, Assigned: warrensomebody)
Details
(Whiteboard: [PDT+] 02/04-Checking on verification with eng)
We should factor the buffering out of nsFileOutputStream and into a separate filter stream, nsBufferOutputStream. nsBufferOutputStream should take another stream to flush to when its buffer becomes full: NS_NewBufferOutputStream(nsIOutputStream* out, nsIOutputStream* *result); (Do we need to do a similar thing for input streams?)
Updated•25 years ago
|
Target Milestone: M15
Comment 1•25 years ago
|
||
setting milestone. we already have buffering in the file stream. We should rip that out and use this method instead.
Assignee | ||
Comment 3•25 years ago
|
||
This needs to get done for beta now since all file i/o is now going through the new file streams we did for nsIFile, and that stuff isn't yet buffered. I've got some code in my tree for this.
Keywords: beta1
Target Milestone: M15 → M14
Assignee | ||
Comment 5•25 years ago
|
||
I just checked in some preliminary code for this. It lives in netwerk/base/public/nsIFileStreams.idl right now. Made the file transport use it. It should speed up caching, and save-as, but I haven't noticed any improvements for reading files (e.g. chrome files). That time is dwarfed by lots of other things (0.03% of runtime).
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
So could this be marked as Verified as far as work done. Or should this be open for more work?
Whiteboard: [PDT+] → [PDT+] 02/04-Checking on verification with eng
Assignee | ||
Comment 7•25 years ago
|
||
Mark it verified.
marking Verified per last comments...thanks! :-)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•