Feature #513
idea for relative AF_UNIX sockets
| Status: | Wontfix | Start: | ||
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | core | |||
| Target version: | - | |||
| Pending: | No |
Resolution: | wontfix |
|
| Patch available: |
Description
Issue #394 closes off the possibility of specifying an AF_UNIX socket as a relative path. But why can't a server.bind that starts with a dot also be interpreted as an AF_UNIX socket? Do AF_INET/AF_INET6 addresses ever start with a dot?
I would appreciate it if you considered this option.
-- chad