Archived

This topic is now archived and is closed to further replies.

Linux (UNIX Socket) with Windows (WinSocket)

This topic is 5892 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I''m just wondering id theyre is any way to have the 2 sockets communicate, or owuld they just do that normally with normal requests........hmm...is that right? I''m using Linux with C++ and saw that the book I''m reading covers UNIX socket so I''m wondering, and ofcourse I got limited experience with Win Socket.

Share this post


Link to post
Share on other sites
They interoperate just fine. The important part is the protocol - for the information transferred to be meaningful, both client and server (or both peers) must be using the same network protocol.

Winsock is actually a Windows-specific implementation of BSD sockets, which is the proper name for UNIX sockets (long live Berkeley Systems Division, Inc.! (BSDi))

Trivia: what were the two "major" variants of UNIX in its early days?

Share this post


Link to post
Share on other sites
Actually, you both perfectly understood and answered my question, thnx.

I''m surprised it worked so well.

As for your trivia....hmmm.......I have no frickin'' clue. I first assumed something like AT&T''s thinger but that wouldnt be one of the first............ by variants I assume you mean distrobutions (if thats what they call them like in linux), then again, linux is a variant of unix (well.....) so.......damnit now me lost is.

Share this post


Link to post
Share on other sites
Actually, UNIX was developed at Bell Labs - which is AT&T! (Remember, we call AT&T Ma'' bell; the company used to be AT&T Bell, then the recursive splits through Bell Atlantic to Verizon...)

So, AT&T was the first major variant. The other was BSD - Berkeley Systems Division - at the University of California at Berkeley. The two used to compete head-to-head in terms of features and functionality (though the code was shared, so they adopted each other''s innovations - such as sockets).

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
quote:
Original post by Oluseyi
Winsock is actually a Windows-specific implementation of BSD sockets, which is the proper name for UNIX sockets (long live Berkeley Systems Division, Inc.! (BSDi))




Can BSD sockets be used with Windows without using Winsock?

Share this post


Link to post
Share on other sites
quote:
Original post by Anonymous Poster
Can BSD sockets be used with Windows without using Winsock?


quote:
From MSDN:

Deviation from Berkeley Sockets


There are a few limited instances where Windows Sockets has had to divert from strict adherence to the Berkeley conventions, usually because of difficulties of implementation in a Windows environment.

It goes on to catalogue all the differences between Windows Sockets and BSD sockets. You can find it at:

MSDN Library
->Platform SDK
->Networking and Distributed Services
->Windows Sockets Version 2
->Windows Sockets Version 2 API
->Overview
->Windows Sockets Programming Considerations
->Deviation from Berkely Sockets

Share this post


Link to post
Share on other sites
quote:
Original post by Sinner_Zero
Well, just to make sure, I was in no way saying Linux was one of the first, HECK no.


I didn''t think so . You were mentally-writing about distributions and such, so I thought I might as well point that out .

[Resist Windows XP''s Invasive Production Activation Technology!]

Share this post


Link to post
Share on other sites