Closed Bug 74104 Opened 19 years ago Closed 15 years ago

nsFileTransport::Cancel needs to call nsIStreamIO::Cancel

Categories

(Core :: Networking, defect)

defect
Not set

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.
Blocks: 64833
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.
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
futuring in favor of bug 74512
Target Milestone: --- → Future
mass move, v2.
qa to me.
QA Contact: tever → benc
OS: Linux → All
Hardware: PC → All
No longer blocks: 64833
marking INVALID.  the code in question no longer exists.
Status: ASSIGNED → RESOLVED
Closed: 15 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.