[JDEV] Re: jabberd 1.4.3 release candidate again
frank at mail.wvnet.edu
Tue Nov 4 20:31:29 CST 2003
Peter G. Millard wrote:
> Frank Seesink wrote:
>>Though I agree that
>>it's strange, from what I can tell, Cygwin does not support IPv6 at
>>this point. The best quote I found, from one Corinna Vinschen, Cygwin
>>Developer, Red Hat Inc., dated 2 Apr 2002 on the Cygwin mailing list:
>>"No INET6 support in Cygwin so far."
> This doesn't seem strange to me... AFAIK, only Windows 2003 server supports
> IPv6 out of the box. Winsock2 doesn't support it, so it's not strange to me
> that cygwin doesn't support it either.
Good point. There is the "Microsoft IPv6 Developer Edition" that's
available in WinXP Pro, but you're right, "out of the box" so far
nothing has it built in except maybe 2003 Server.
It would be nice if (assuming it's possible) some of the functionality
that apparently the Jabberd 1.4.x coders tapped into were somehow
wrapped or mimicked in Cygwin. Both Jabberd 1.4.x and the new Jabberd2
(not to mention a few other *nix-based projects) seem to rely on
functions such as inet_ntop(), even though I would suspect almost all
usage is in the IPv4 space.
Again, I don't code for a living. And I definitely don't know the ins
and outs of Cygwin's core or code at that level (though it's pretty
clear that some differences in OS archictecture are apparently quite
difficult to emulate...like *nix fork() in Cygwin). So I'm not really
in a position to even say "Why don't they have XYZ in Cygwin?", as there
might be a darn good reason.
At best I hack with application level code, and that's only when
personally motivated enough like with Jabber. I wanted an open-source,
open-standard IM protocol as the base for a dept. IM server. Jabberd
was what really caught my eye. But I'm stuck in a Windows world for the
moment, so decided to have a go at it using Cygwin. And here I am.
Damn computers. :-)
More information about the JDev