From: mert0407 AT sable DOT ox DOT ac DOT uk (George Foot)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Winsock or TCP/IP
Date: 29 Jul 1997 22:03:38 GMT
Organization: Oxford University, England
Lines: 29
Message-ID: <5rlpbq$sb3@news.ox.ac.uk>
References: <01ILOAJFZNQM904SW6 AT InfoAve DOT Net> <33DB994A DOT 7D7B AT cornell DOT edu>
NNTP-Posting-Host: sable.ox.ac.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

A. Sinan Unur (asu1 AT cornell DOT edu) wrote:
: storm3 wrote:

: >I need to know which library I should use the WSOCK or TCP/IP
: > lib.. I am gonna be running these under '95 and would like them to be 
: > able to talk to each other when I connect using '95's dial up 

: AFAIK, the purpose of the WSOCK library available for djgpp is to enable
: djgpp apps to make winsock calls. (someone correct me if i am wrong.)

Not quite. Well, I can't speak for Dan Hedlund's intentions of course, but
the library provides a class with some common winsock functions as
methods. It's a bit like an extra wrapper for each connection. The source
code does, of course, enable you to make the calls directly, yourself. A
while ago I was considering making a strict C only version which would
provide all the standard Winsock functions without the class wrapper, but
I never found time.

This would be a good thing because it would simplify porting programs from
other environments, and people learning winsock this way could then go to
other environments more easily. At present, the porting isn't too hard if
you know what you're doing. 

Incidentally, Winsock is not restricted to TCP - you can also do UDP. I'm
not sure whether you can use raw sockets, though; I think not.

-- 
George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Merton College, Oxford