Closed
Bug 24435
Opened 26 years ago
Closed 24 years ago
socket transport needs synchronous DNS failure for Open*Stream() methods.
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
INVALID
People
(Reporter: jud, Assigned: gordon)
References
()
Details
(Whiteboard: [nsbeta2-]3 days)
Attachments
(1 file)
|
4.90 KB,
patch
|
Details | Diff | Splinter Review |
Currently there is no way for synchronous users (those who use
OpenInput|OutputStream() of the socket transport to receive DNS failure codes.
This causes ftp:// urls with unknown hosts to report no status.
I propose that the socket transport implementations of Open*Stream() block until
a host is found/not found. The idea of the user sucessfully getting a stream on
a socket that doesn't even exist is not good.
Comment 1•26 years ago
|
||
Good call. You're right, we do need to block the streams until we get the dns
callback.
| Reporter | ||
Comment 2•26 years ago
|
||
I'm working on a fix for this.
Assignee: rpotts → valeski
Target Milestone: M14
| Reporter | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
| Reporter | ||
Comment 3•26 years ago
|
||
I'm attatching a proposed patch. This patch adds two member vars to the socket
transport. One is a flag indicating whether or not a lookup has completed, and
the other is a nsresult reserved for the return value of Open*Stream().
Rick, I've also un-commented the code that adds the transport instance to the
work Q for an OpenOutputStream() call. I may very well have been the one that
suggested we pull this out, but I don't recall..??
| Reporter | ||
Comment 4•26 years ago
|
||
| Reporter | ||
Updated•26 years ago
|
Target Milestone: M14 → M15
| Reporter | ||
Comment 5•26 years ago
|
||
linux is having problems with this patch. off to m16
Target Milestone: M15 → M16
| Reporter | ||
Updated•26 years ago
|
Whiteboard: 3 days
| Reporter | ||
Comment 7•26 years ago
|
||
fix finally in.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 8•26 years ago
|
||
backed out changes
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•26 years ago
|
||
why?
| Reporter | ||
Comment 10•26 years ago
|
||
there was some intermittant loading problem w/ edit page and compose window and
apparently imap was having trouble.
| Reporter | ||
Comment 11•26 years ago
|
||
fixed.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 12•26 years ago
|
||
we're baaaack. I need to rework this patch considerably.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 13•26 years ago
|
||
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: 3 days → [nsbeta2+]3 days
Comment 14•26 years ago
|
||
Per today's PDT Networking QA review, moving from [nsbeta2+] to [nsbeta2-]
Whiteboard: [nsbeta2+]3 days → [nsbeta2-]3 days
| Reporter | ||
Updated•25 years ago
|
Target Milestone: M17 → mozilla1.0
| Reporter | ||
Comment 15•25 years ago
|
||
-> doug. I'm not sure this is even a bug anymore w/ the new api changes.
Assignee: valeski → dougt
Status: REOPENED → NEW
Comment 17•25 years ago
|
||
what is milestone "mozilla1.0" anyway? Moving to future.
Target Milestone: mozilla1.0 → Future
Comment 18•25 years ago
|
||
gordon implemented the dns client in mozilla. over to him
Assignee: dougt → gordon
| Assignee | ||
Comment 19•24 years ago
|
||
After talking to Darin, we've decided this bug is not applicable anymore.
Marking INVALID.
Status: NEW → RESOLVED
Closed: 26 years ago → 24 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•