Closed
Bug 796120
Opened 14 years ago
Closed 14 years ago
UnixSocketConsumers cannot detect connect/accept errors
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 796176
| blocking-basecamp | + |
People
(Reporter: qdot, Assigned: qdot)
References
Details
Due to the fact that both connect/accept are non-blocking now, UnixSocketConsumers need a way to be notified if there was an error in connecting/accepting. Currently they just consider things to always connect, which causes crashes.
| Assignee | ||
Updated•14 years ago
|
Summary: [b2g-bluetooth] UnixSocketConsumers cannot detect connect/accept errors → UnixSocketConsumers cannot detect connect/accept errors
| Assignee | ||
Comment 3•14 years ago
|
||
Callbacks came in with bug 796176 and bug 800247.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•