Closed Bug 12892 Opened 25 years ago Closed 25 years ago

eliminate NS_BASE_STREAM_EOF

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: warrensomebody, Assigned: warrensomebody)

References

Details

Brendan and I decided that EOF should be denoted by the read/write-count
out-parameter being 0, not a success or failure nsresult code. This will allow
JS authors to call Read/Write on streams with less overhead.

Also, NS_BASE_STREAM_WOULD_BLOCK should become a failure code. This will cause
an exception in JS, and require callers to deal with latent streams more
explicitly.
Target Milestone: M11
Fixes in my tree.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
done
Status: RESOLVED → VERIFIED
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
You need to log in before you can comment on or make changes to this bug.