Op Wed, 26 Sep 2012, schreef Jeff Rogers:
I'm not well versed in pv6, but one concern I have about your patch is that
it looks like it changes everything to support only ipv6, with ipv4 in
compatibility "mapped" mode. Could that break compatibility for some older
systems? Do we care?
The patch requires that the libc supports the ipv6 API's, but not that the
operating system has ipv6 support. For example, you can compile you Linux
kernel without ipv6 support and it will still happily do ipv4 only.
So, to make it clear, you have 100% support for IPV4 only systems with
this patch applied.
I think you have to go quite a way back into the past to find a libc
without ipv6 support, ipv6 was added to Linux in the 1990's. I not
worrying about FreeBSD's ipv6 support either.
There might be some old servers running a commercial Unix with a libc with
ipv6 support. I am tempted to say I'd first like to see if they actually
exists, rather than taking steps beforehand...
...because: Should we need to support both API's, the the best way is to
put all modification inside #ifdef. That is not nice from a code
maintenance point of view.
Daniël
------------------------------------------------------------------------------
How fast is your code?
3 out of 4 devs don\\\'t know how their code performs in production.
Find out how slow your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219672;13503038;z?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
