> > Do you have an idea for a test which I could adapt to open a socket > > using Winsock and use/access it via standard BSD sockets afterwards > > (obviously, that test would need to use the respective sockets API > > rather than Synapse)? > > > I haven't touched OS/2 since 1993 :) From your previous message, I > learned that winsock is a compatibility layer. I'm just trying to ask > the right questions to get more information on what is going wrong. As > a test you could perhaps temporarily patch TBlockSocket.SendBuffer to > use the bsd send instead of synsock.Send. If the handle is > transparent, fetching a http page should just work.
Do not reinvent a wheel. Synsock is just API functions layer between a Synapse and system sockets. TBlockSock.Handle is system socket handle. TBlockSock is just object based encapsulation of sockets API. Synsock provide common socket interface for rest of Synapse units. It is implemented as direct winsock calls, or it calls related functions from the FreePascal's Sockets unit. So, when somethink working fine with system socket API, no reason why it should not work with Synsock. -- Lukas Gebauer. http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib. http://geoget.ararat.cz/ - Geocaching solution ------------------------------------------------------------------------------ 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
