Results 1 to 5 of 5

Thread: Winsock API functions and non-prefixed WSA

  1. #1
    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

  2. #2
    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 ().

  3. #3
    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?

  4. #4
    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.

  5. #5
    Join Date
    Dec 2008
    Posts
    161

    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.
    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.

Similar Threads

  1. Netsh winsock reset
    By Saaz in forum Operating Systems
    Replies: 4
    Last Post: 08-12-2011, 05:31 AM
  2. Problems with Winsock provider catalog
    By No. 4 in forum Windows XP Support
    Replies: 6
    Last Post: 24-05-2010, 06:56 PM
  3. netsh winsock reset command for Mac OS X
    By CossFire in forum Operating Systems
    Replies: 4
    Last Post: 24-02-2010, 10:04 PM
  4. kernel32.dll, winsock.dll, wsock32.dll
    By skpanda in forum Networking & Security
    Replies: 5
    Last Post: 30-07-2009, 04:48 PM
  5. Winsock library Error 10107
    By Rodney123 in forum Operating Systems
    Replies: 4
    Last Post: 21-02-2009, 11:07 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •