On Saturday 09 December 2000 20:17, Dave Johnson wrote:
> While porting an application to cygwin I've discovered the following:
>
> After a non-blocking connect() is called for a TCP connection I am
> calling getsockname() to determine the IP on the local size of the
> connection attempt.
>
> After calling getsockname() and getting the IP address from
> ..sin_addr.s_addr of the sockaddr_in structure the IP was filled out
> with 0's instead of the IP address of the interface in which the
> connection attempt is going out on.
>
> Doing another getsockname() after the socket becomes writable and the
> connection is completed returns valid data.
>
> Other UNIX OS's will return valid socket information after a
> non-blocking connect(). Is this a limitation of cygwin or a bug?
It's a limitation of Winsock. It could perhaps been worked around
in Cygwin. Patches are welcome.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:[EMAIL PROTECTED]
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
--
Want to unsubscribe from this list?
Send a message to [EMAIL PROTECTED]
