Closed
Bug 74104
Opened 24 years ago
Closed 20 years ago
nsFileTransport::Cancel needs to call nsIStreamIO::Cancel
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
VERIFIED
INVALID
Future
People
(Reporter: jud, Assigned: darin.moz)
Details
This will allow blocking reads on the file transport to unblock when the load is cancelled.
Assignee | ||
Comment 1•24 years ago
|
||
With multiple threads, the solution to this problem is non-trivial. As I understand this bug to apply more so to Read's which might block for relatively long periods of time, I'd suggest that such nsIInputStream impl's become non-blocking. Then, let's fix the file transport to make it work with non-blocking streams. That way, we are not hogging a file transport thread for nothing. A non-blocking solution would be much better (and possibly the only solution) if and when the file transport moves from a thread pool to running directly on the callers thread.
Assignee | ||
Comment 2•24 years ago
|
||
moving forward on making the file transport support non-blocking streams, instead of trying to solve the blocking-read/write cancelation problem.
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•20 years ago
|
||
marking INVALID. the code in question no longer exists.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•