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
-- Android Development Center
-- Cloud Development Project Center
-- HTML5 Development Center
-- Windows Mobile Development Center