Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!haven.umd.edu!udel!princeton!siemens!demon!jrv
From: jrv@demon.siemens.com (James R Vallino)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Socket call in Window 3.0 program
Message-ID: <63927@siemens.siemens.com>
Date: 21 Jun 91 14:46:20 GMT
References: <1995@nixsin.UUCP> <1991Jun19.141519.5669@odi.com>
Sender: news@siemens.siemens.com
Reply-To: jrv@demon.siemens.com
Organization: Siemens Corporate Research, Inc.
Lines: 23

In article <1991Jun19.141519.5669@odi.com> ed@odi.com (Ed Schwalenberg) writes:
>I haven't found other vendors yet with socket libraries for Windows.
>I saw an ad for some company, but it wasn't yet released and had high
>per-user royalties.
>
>If there's a better way, I'd sure like to know about it.

Wollongong has just started shipping PathWay Access for DOS Release 1.1
which includes a sockets library interface when you get their API toolkit.
This is a first release of the Windows compatible library so things may be a
little shaky.

NetManage (408-257-6404) also has a Windows compatible TCP/IP software
development kit which includes a sockets interface.  This product is in its
second or third release so maybe the bugs have been worked out by now.

I have used the Wollongong non-Windows API previously and have never used
the NetMange product.
--
Jim Vallino	Siemens Corporate Research, Inc., Princeton, NJ
jrv@demon.siemens.com
princeton!siemens!demon!jrv
(609) 734-3331