Closed Bug 34359 Opened 24 years ago Closed 24 years ago

There's something wrong with timeouts on nsSocketTransport

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
x86
All
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: ruslan, Assigned: ruslan)

Details

There's something wrong with timeouts on nsSocketTransport. They don't seem to 
work all the time. Need to investigate
Status: NEW → ASSIGNED
Target Milestone: --- → M15
Ok. The time out only works on Connect and never on Read. Warren, Should we 
timeout on read too? I think we should.
perhaps on a related note: bug 34239 - it almost seems as a timeout is
*provoked* to activate there - premature.
I agree that we should.
Now fixed. We need to make it adjustable on per-protocol basis. I'll file a 
separate bug.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
VERIFIED:
This bug would block Bug 34547:

  Need to be able to configure nsSocketTimeout

Which is VERIFIED/FIXED already.
Status: RESOLVED → VERIFIED
QA Contact: tever → benc
You need to log in before you can comment on or make changes to this bug.