Re: socket api problem: can't bind an ipv6 socket to ::ffff:0.0.0.0

Top-posting so others can see your off-list rant in full.  I see no reason to
help you any further, even though I did have a patch that would change this
behavior for you.  Good luck with your "biggest noncommercial Internet messaging
infrastructure" in the world.

-Brian

Felix von Leitner wrote:

quoted

Please show me a porting guide that even mentions supporting IPv4-only mode
through an IPv6 socket by using this method.  There is none that I know of.

Are you kidding me?
A _porting guide_?!?

If you are trying to troll me, you just succeeded.

Now please make room so the adults can talk about the issue at hand
while you are putting up straw men.

quoted

quoted

Did I mention *BSD and OSX allow this?

That was their decision, and it doesn't mean it's the right thing to do.

Riiiight.

There is an old joke.  The Joneses are driving on the freeway, when the
radio sounds a warning.  "Warning!  There is a car driving the wrong way
on the freeway!"  Says grandpa (who is driving the car) "what do you
mean, one guy?  Hundreds!!"

Sometimes, if there are two ways to read something, and your users tell
you which way they want it, and the competition does it the way the
users want, and you don't, sometimes, in that case, YOU ARE WRONG.

It's that easy.

Hey, you have an hp.com email address.  Why don't you check out how
HP-UX handles this.

quoted

Compare your bittorrent server to Apache, which is probably the most widely-used
server application in the world.  It doesn't do what you're trying to do.  See
http://httpd.apache.org/docs/2.2/bind.html and/or browse the source code.

What is this supposed to be?  Name dropping?

I'm not impressed.

And Apache never won any speed or scalability records.  Just because
many people use Apache does not mean it's a good piece of software.  You
know, many more people use Windows than Linux.  That does not make
Windows the standard to follow.  Hey, many people use sendmail!  And
BIND!

Felix