On 10 Dec 12, at 17:52, Tomas Hajny wrote: > On Mon, December 10, 2012 14:24, Ludo Brands wrote: > >> There should be no C runtime involved when accessing the standard OS/2 > >> API > >> (which includes both the native BSD sockets and the Winsock > >> compatibility > >> layer). Whatever is done when using EMX libc, it must still go through > >> this OS/2 API in the end. However, I understand that there may be some > >> socket initialization involved on the EMX libc side (this indeed seems > >> to > >> be the case as suggested by peeking into > >> http://svn.netlabs.org/repos/libc/branches/libc-0.6/src/emx/src/os2/tcpip.c > >> - really bad, all this ugly world of mixing file and socket handles > >> together on a platform having these concepts completely separated :-( ). > >> I'll see what I could do (probably start by extending the previous test > >> to > >> import the "send" call from EMX libc). It would be the best to just > >> allocate the fake "file" handle expected by EMX libc to the existing > >> socket number if necessary (i.e. if OpenSSL is involved), but I'm afraid > >> that the respective EMX libc function (tcpip_new_handle) may not be > >> exported / accessible externally. Too bad. :-(
It seems that there is a call published by the EMX runtime for importing an externally opened socket handle, so this might be the best solution. I'll play with it once I find the needed time and let you know the results. Thanks again Tomas ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
