Re: Bug#667737: libnet-server-perl: no IPv4 server when binding to localhost
Oops, this were a draft email which I were unsatisfied with because it
sounded a bit harsh. Planned to save it and continue editing it today,
but it were unfortunately sent. Please disregard the last email.
> A bit late maybe, but...
>> At its core, there's a concern here that asking a server to bind to a
>> name might actually bind it to multiple addresses (since a name can have
>> multiple addresses). I'm not convinced that Net::Server can be properly
>> made to bind to multiple addresses with a single "host" configuration,
>> but i agree that for the sake of congruity with the rest of the perl
>> world, Net::Server should preferentially bind to the IPv4 address if a
>> given name maps to both an IPv4 and an IPv6 address.
What I mean to say is:
I understand the wish to ensure IPv4 functions as good as possible
today, because that's what over 99% of the users use. The logical
short term solution is then to disable IPv6 whenever some conflict
surface. Unfortunately this short term focus mean Debian (once again)
risk to miss the release goal of full IPv6 support.
It makes more sense to fix the lack of IPv6 in HTTP::Daemon than to
disable it in Net::Server.
> If folks feel like this would address the problem described in this
> ticket, i'm happy to try to bump the Net::Server IPv6 overhaul up in my
I think it might be better to add IPv6 support in other modules than
fixing problems (which isn't true problems) in this one.
> I'd be happy to collaborate with anyone interested on it, of course.
While not being apart of the perl-group I do volunteer to help out,
especially things around IPv6 (which I do care about). Now there isn't
that many perl modules with bugs tagged with ipv6...
"D’ä e å, vett ja”, skrek ja, för ja ble rasen,
”å i åa ä e ö, hörer han lite, d’ä e å, å i åa ä e ö"
- Gustav Fröding, 1895