WinSock OCX vs API - SPEED!?


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: WinSock OCX vs API - SPEED!?

  1. #1
    rhwiebe Guest

    WinSock OCX vs API - SPEED!?


    Have an app that uses WinSock.ocx for communications across client
    network. Client insists that SPEED is NB!
    Client does NOT believe that speed is dependent on network, how
    busy, etc. and is CONVINCED that writing a custom DLL (probably
    in VC) will speed comms. Personally, I DO NOT BELIEVE!
    Anyone know anything you would like to tell me?
    API calls to the WinSock32.dll? Faster than OCX?
    (I understand that the 32 is a thunk to call the 16 bit version,
    which I understand to be the real comms. True? Is the OCX then
    also a thunk? Or does it call the 32 bit DLL ....?)
    All info welcome. Thanks



  2. #2
    Monte Hansen Guest

    Re: WinSock OCX vs API - SPEED!?

    I'm not familiar with the "winsock.ocx". Do you mean MSWINSCK.OCX? Try
    loading the OCX in Dependency Walker (in your Tools Start menu).

    Also, if this is a client/server app (with multiple clients connecting to a
    single server), I think you will find that the design of your server
    component is far more crucial.

    +|+|+|+|+|+|+|+|+|+|+|+|+|+|+|+
    Monte Hansen
    http://KillerVB.com
    +|+|+|+|+|+|+|+|+|+|+|+|+|+|+|+


    "rhwiebe" <rhwiebe@usa.net> wrote in message
    news:3b14258e$1@news.devx.com...
    >
    > Have an app that uses WinSock.ocx for communications across client
    > network. Client insists that SPEED is NB!
    > Client does NOT believe that speed is dependent on network, how
    > busy, etc. and is CONVINCED that writing a custom DLL (probably
    > in VC) will speed comms. Personally, I DO NOT BELIEVE!
    > Anyone know anything you would like to tell me?
    > API calls to the WinSock32.dll? Faster than OCX?
    > (I understand that the 32 is a thunk to call the 16 bit version,
    > which I understand to be the real comms. True? Is the OCX then
    > also a thunk? Or does it call the 32 bit DLL ....?)
    > All info welcome. Thanks
    >
    >




  3. #3
    Monte Hansen Guest

    Re: WinSock OCX vs API - SPEED!?

    I'm not familiar with the "winsock.ocx". Do you mean MSWINSCK.OCX? Try
    loading the OCX in Dependency Walker (in your Tools Start menu).

    Also, if this is a client/server app (with multiple clients connecting to a
    single server), I think you will find that the design of your server
    component is far more crucial.

    +|+|+|+|+|+|+|+|+|+|+|+|+|+|+|+
    Monte Hansen
    http://KillerVB.com
    +|+|+|+|+|+|+|+|+|+|+|+|+|+|+|+


    "rhwiebe" <rhwiebe@usa.net> wrote in message
    news:3b14258e$1@news.devx.com...
    >
    > Have an app that uses WinSock.ocx for communications across client
    > network. Client insists that SPEED is NB!
    > Client does NOT believe that speed is dependent on network, how
    > busy, etc. and is CONVINCED that writing a custom DLL (probably
    > in VC) will speed comms. Personally, I DO NOT BELIEVE!
    > Anyone know anything you would like to tell me?
    > API calls to the WinSock32.dll? Faster than OCX?
    > (I understand that the 32 is a thunk to call the 16 bit version,
    > which I understand to be the real comms. True? Is the OCX then
    > also a thunk? Or does it call the 32 bit DLL ....?)
    > All info welcome. Thanks
    >
    >




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center