Go Back   TechArena Community > Software > Software Development
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



Winsock API functions and non-prefixed WSA

Software Development


Reply
 
Thread Tools Search this Thread
  #1  
Old 23-04-2009
Member
 
Join Date: Apr 2009
Posts: 61
Winsock API functions and non-prefixed WSA
  

Hello,

I'm looking for an explanation of the difference between the WSA and their equivalents without the WSA.

For example the difference between select and WSASelect etc ...

Thank you for your reply

Reply With Quote
  #2  
Old 23-04-2009
Member
 
Join Date: Mar 2008
Posts: 227
Re: Winsock API functions and non-prefixed WSA

I am not sure, but it is possible that the first WSA functions have arisen before Microsoft publish functions that are compatible with Berkeley sockets.

To read, I usually only the non-WSA functions, except for asynchronous WSAEventSelect () and its sisters and WSAAsyncSelect ().
Reply With Quote
  #3  
Old 23-04-2009
Member
 
Join Date: Apr 2009
Posts: 61
Re: Winsock API functions and non-prefixed WSA

So if we want to make a portable application on unix it is better to use functions such as socket, select, send_to, recev_from etc. .... or the only change will be a typedef int SOCKET; not?
Reply With Quote
  #4  
Old 23-04-2009
Member
 
Join Date: Dec 2008
Posts: 70
Re: Winsock API functions and non-prefixed WSA

typedef int SOCKET; and # define closesocket close, not to mention the WSAStartup () / WSACleanup () on Windows.
And I have yet to forget, it is best to consult the sample code of provided by most of user freely on the internet.
Reply With Quote
  #5  
Old 23-04-2009
Member
 
Join Date: Dec 2008
Posts: 161
Re: Winsock API functions and non-prefixed WSA

Quote:
I am not sure, but it is possible that the first WSA functions have arisen before Microsoft publish functions that are compatible with Berkeley sockets.
No, Winsock compatible BSD since version 1.0. The real contribution in relation to the functions BSD is a better compatibility with Windows. For example, send waiting for the address of a buffer containing the data to be sent and a parameter int indicating the size of this buffer. WSASend expects a pointer to type structures WSABUF. It actually code faster, or at least simply using WSASend instead of send.
Reply With Quote
Reply

  TechArena Community > Software > Software Development
Tags: , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Winsock API functions and non-prefixed WSA"
Thread Thread Starter Forum Replies Last Post
Netsh winsock reset Saaz Operating Systems 4 08-12-2011 05:31 AM
Problems with Winsock provider catalog No. 4 Windows XP Support 6 24-05-2010 06:56 PM
netsh winsock reset command for Mac OS X CossFire Operating Systems 4 24-02-2010 10:04 PM
kernel32.dll, winsock.dll, wsock32.dll skpanda Networking & Security 5 30-07-2009 04:48 PM
Winsock library Error 10107 Rodney123 Operating Systems 4 21-02-2009 11:07 AM


All times are GMT +5.5. The time now is 03:54 PM.