Mladen Turk wrote:
> Markus Schönhaber wrote:
> > Mladen Turk wrote:
> >
> > BTW: why is this situation special wrt the native connector?
>
> Right, but that's not the case for all supported OS-es.
> Windows for sure (and Solaris I think) will refuse
> 127.0.0.1 when the address="::"
Do I understa
Remy Maucherat wrote:
Comments?
As you say, 0.0.0.0 is ipv4 so it looks like a bad default value to me,
while null means whatever the connector wants. Internally, it's up to
the native layer to figure it out, I think.
Sure, but the fact is that Java connectors will always
use IPV4. APR c
Markus Schönhaber wrote:
Mladen Turk wrote:
BTW: why is this situation special wrt the native connector?
Right, but that's not the case for all supported OS-es.
Windows for sure (and Solaris I think) will refuse
127.0.0.1 when the address="::"
Regards,
Mladen.
--
Mladen Turk wrote:
> With Native connector if the OS supports IPV6 the
> default address (null) is translated to "::", thus
> it only listens to the IPV6 addresses. In case the
> OS doesn't support IPV6 (hardly to be found nowadays), the
> null address is equivalent to the address="0.0.0.0".
> The
Mladen Turk wrote:
Hi,
With Native connector if the OS supports IPV6 the
default address (null) is translated to "::", thus
it only listens to the IPV6 addresses. In case the
OS doesn't support IPV6 (hardly to be found nowadays), the
null address is equivalent to the address="0.0.0.0".
The same
Hi,
With Native connector if the OS supports IPV6 the
default address (null) is translated to "::", thus
it only listens to the IPV6 addresses. In case the
OS doesn't support IPV6 (hardly to be found nowadays), the
null address is equivalent to the address="0.0.0.0".
The same is for any Java conn
