Overview
| Artifact ID: | afb5164b9cef139cb1b7b665809a0475eb7d3962 |
|---|---|
| Ticket: | 5425f2c08257f7d9660276c4c8f764ad2d178e1c
Async socket connect may flag error and still connects |
| User & Date: | max 2013-11-12 13:27:29 |
Changes
- closedate changed to: "2456609.06075973"
- closer changed to: "max"
- icomment:
Fixed in [80ca9fe746] and [f644fb5a9f]. When implementing multi-address [socket -async], I thought it would only be used together with fileevent, and [fconfigure -error] would not be called before the readable event has fired. But now I see that -async without fileevent even makes sense, e.g. to trace the addresses that were tried and why each of them failed, so the error caching (reading SO_ERROR is destructive) needs to go both ways, from the event handler hidden behind [socket -async] to [fconfigure -error] and vice versa.
- login: "max"
- mimetype: "text/plain"
- status changed to: "Closed"