Understand how software connects to socket device

Discussion in 'C++' started by gtrava01, Jun 25, 2010.

  1. gtrava01

    gtrava01 New Member

    Joined:
    Jun 25, 2010
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    I am trying to understand how demo software connects to a device for controls. I'm told that C++ bindings to windows dynamic libraries is necessary and have bene sent a *.h file which contains as an example:

    / / Function interface
    / / Initialize dynamic link library
    DLL_DECL BOOL SDK_InitSystem ();
    DLL_DECL BOOL SDK_IsInited ();
    / / Unloading dynamic link library
    DLL_DECL void SDK_CloseSystem ();
    / / Callback function prototype information
    typedef void (CALLBACK * MTCSDKCALLBACKFUNC) (DWORD dwMsgID, WPARAM wParam, LPARAM lParam);
    / / Register callback function message
    DLL_DECL BOOL SDK_RegisterCallBackFunc (MTCSDKCALLBACKFUNC CallBackFunc);
    / / Connect Terminal
    DLL_DECL BOOL SDK_ConnectMT (DWORD dwMTIP);

    I presume these functions exist in the device and are called somehow via a socket connection created in a winsock program which links in the .h file?

    I'm not a programmer, just trying to understand how this might work.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice