On 12/12/06, Bob Rossi <[EMAIL PROTECTED]> wrote:
On Sun, Dec 10, 2006 at 08:42:29PM +1100, John Vandenberg wrote:
> On 12/9/06, Bob Rossi <[EMAIL PROTECTED]> wrote:
> >On Wed, Dec 06, 2006 at 09:07:20AM +1100, John Vandenberg wrote:
> >> We should first check whether the libtool developers inten
Mladen Turk wrote:
> Colm MacCarthaigh wrote:
>>> Are you sure?
>>> Pass the NULL on unix enabled IPV6 APR, it will accept the
>>> 127.0.0.1. The IPV6 enabled Win32/Win64 will always reject this.
>>
>> apr_sockaddr_t is a linked list, and you have to listen() on every
>> address in the list.
>
On Mon, Dec 11, 2006 at 05:00:27PM +0100, Mladen Turk wrote:
> Makes no sense to continue the discussion because you either
> have not tried to build the APR with IPV6 enabled on Windows,
> or you just do not understand what the cross-platform is.
Given I *wrote* much of that code, and made it wor
Colm MacCarthaigh wrote:
On Mon, Dec 11, 2006 at 04:48:23PM +0100, Mladen Turk wrote:
Colm MacCarthaigh wrote:
Are you sure?
Pass the NULL on unix enabled IPV6 APR, it will accept the
127.0.0.1. The IPV6 enabled Win32/Win64 will always reject this.
apr_sockaddr_t is a linked list, and you have
On Mon, Dec 11, 2006 at 04:48:23PM +0100, Mladen Turk wrote:
> Colm MacCarthaigh wrote:
> >>>
> >>Are you sure?
> >>Pass the NULL on unix enabled IPV6 APR, it will accept the
> >>127.0.0.1. The IPV6 enabled Win32/Win64 will always reject this.
> >
> >apr_sockaddr_t is a linked list, and you have to
Colm MacCarthaigh wrote:
Are you sure?
Pass the NULL on unix enabled IPV6 APR, it will accept the
127.0.0.1. The IPV6 enabled Win32/Win64 will always reject this.
apr_sockaddr_t is a linked list, and you have to listen() on every
address in the list.
Look, I'm I speaking Marsian?
Same API
On Mon, Dec 11, 2006 at 04:30:43PM +0100, Mladen Turk wrote:
> Colm MacCarthaigh wrote:
> >
> >> So you are saying that the same API behaves differently
> >> depending on the OS beneath. Then what's the purpose of the APR?
> >
> > No, the API behaves no differently at all. The API deals with you
>
Colm MacCarthaigh wrote:
>
>> So you are saying that the same API behaves differently
>> depending on the OS beneath. Then what's the purpose of the APR?
>
> No, the API behaves no differently at all. The API deals with you
> wanting to listen on the ANY just fine, on windows and so on it will
> r
On Mon, Dec 11, 2006 at 03:41:55PM +0100, Mladen Turk wrote:
> Colm MacCarthaigh wrote:
> >On Mon, Dec 11, 2006 at 02:58:04PM +0100, Mladen Turk wrote:
> >>On WIN32, APR by default comes with IPV6 disabled.
> >
> >I'm not sure what you mean by that. Do you mean the binary builds
> >particular devel
Colm MacCarthaigh wrote:
On Mon, Dec 11, 2006 at 02:58:04PM +0100, Mladen Turk wrote:
On WIN32, APR by default comes with IPV6 disabled.
I'm not sure what you mean by that. Do you mean the binary builds
particular developers make?
Yes and no. IPV6 on WIN32/WIN64 can be enabled only by
manua
On Mon, Dec 11, 2006 at 02:58:04PM +0100, Mladen Turk wrote:
> On WIN32, APR by default comes with IPV6 disabled.
I'm not sure what you mean by that. Do you mean the binary builds
particular developers make?
> Now, this is completely platform dependent, and makes
> the same config behaving differ
On Sun, Dec 10, 2006 at 08:42:29PM +1100, John Vandenberg wrote:
> On 12/9/06, Bob Rossi <[EMAIL PROTECTED]> wrote:
> >On Wed, Dec 06, 2006 at 09:07:20AM +1100, John Vandenberg wrote:
> >> We should first check whether the libtool developers intentionally
> >> added that blank line; if they can fix
Hi,
On WIN32, APR by default comes with IPV6 disabled.
Enabling IPV6 brings in the completely different
behavior for NULL Listen address.
While on unixes regardless of the address being
NULL or 0.0.0.0 the socket will always accept
the connection to 127.0.0.1.
On Windows, if IPV6 is enabled the c
13 matches
Mail list logo
