The SuperCom DUAL API

*Application Programing Interface (API)

F: What is the SuperCom DUAL API ?
A: The SuperCom DUAL API consists of the DLL API and the ActiveX API.
ActiveX API: The ActiveX API consists of Properties and Methods provided by one ActiveX control. The ActiveX API is available automatically after installation within the development environment i.e. Visual Basic, VBA, Visual C++, C++ Builder, C#, VB .net, Delphi etc.
DLL API: The DLL API is the combination of one or more runtime files (.DLL) and the corresponding import library (.LIB, .BAS, .PAS, .TPU etc.). The import library is inserted into the applications project and compiled. This way the application gains access to the functions located inside the DLL. The DLL is an external shared library of functions that is loaded when needed. A DLL takes code out of the executable, makes it smaller, it loads faster and it can be shared by many executables the same time. Windows automatically loads the DLL when the application calls for it. The most part of the Windows operating system consist of DLLs (Windows API). DLL's are maybe the most useful feature ever added to Windows and is the abutment of the Windows modularity concept. Thus the SuperCom DLL API fits excellent in the Windows modularity concept and using is very easy.

With DUAL API you can choose to use one API or even both API's as it fits best.

DLL API

ActiveX API

Features List

Features List

Functions

Properties


Using SuperCom in Microsoft .NET Framework (e.g. C#, VB Net) reveals another SuperCom API, which is compatibel to the well known SuperCom API. So nothing additionally to learn but the new class library offers a lot more. Developers can now use the DLL API and the ActiveX API via the SuperCom .NET Class Library and even combine both API as needed. Thus the SuperCom ActiveX is not needed in order to use the ActiveX API.

Despite the new functionality in the class library, the SuperCom ActiveX is still supported with .NET.

The SuperCom .NET Class Library is included in every DLL API and DUAL API SuperCom completely with its C# source code! The SuperCom .NET Class Library is avalable in 32bit and 64bit SuperCom.

 

The Chart of Software and Features shows which SuperCom product supports a specific API. A DUAL API product supports both (ActiveX API and DLL API).

 

F: What is the SuperCom ActiveX API ?
A: The ActiveX API consists of Properties and Methods provided by one ActiveX control. The ActiveX API is available automatically after installation within the development environment i.e. Visual Basic, VBA, Visual C++, C++ Builder, C#, VB .net, Delphi etc.

Features List

Properties


The Chart of Software and Features shows which SuperCom product supports a specific API.

 

F: What is the SuperCom DLL API ?
A: The DLL API is the combination of one or more runtime files (.DLL) and the corresponding import library (.LIB, .BAS, .PAS, .TPU etc.). The import library is inserted into the applications project and compiled. This way the application gains access to the functions located inside the DLL.
DLL: The DLL is an external shared library of functions that is loaded when needed. A DLL takes code out of the executable, makes it smaller, it loads faster and it can be shared by many executables the same time. Windows automatically loads the DLL when the application calls for it. The most part of the Windows operating system consist of DLLs (Windows API). DLL's are maybe the most useful feature ever added to Windows and is the abutment of the Windows modularity concept. Thus the SuperCom DLL API fits excellent in the Windows modularity concept and using is very easy.

Features List

Functions


The Chart of Software and Features shows which SuperCom product supports a specific API.

 

F: Do I have to choose an API in advance ?
A: Users of a SuperCom DUAL API software package are in position to select the most suitable API or they can use the ActiveX properties and methods and also call DLL functions. By combining both APIs a very big function set is available to the application. It opens unforeseen potentialities. For instance while the application administrates the data link using the high level ActiveX properties it can call DLL functions to perform low level tasks. Using low level DLL functions it's even possible to enhance or change the behavior of the event reporting mechanism within the ActiveX. The DLL API also includes intelligent high level functions which may run faster or offer more possibilities that the corresponding ActiveX property or method.

 

F: Can I use SuperCom functions and protocols in combination with a third-party communication toolkit ?
A: The SuperCom DLL API provides functions to integrate connections and/or links established with a third-party toolkit into SuperCom. For instance an application uses a TCP component to connect to a server but needs ZMODEM capabilities. Several samples available.
NOTE: Since not all configurations are possible and not all components are providing the links or data needed, we suggest you to contact our technical support and discuss the matter.

 

F: Do I have any influence on the event reporting mechanism ?
A: Yes, both APIs offer properties and functions to suppress unwanted events. Using the DUAL API it's even possible to enhance or change the behavior of the event reporting mechanism within the ActiveX by using the DLL API as shown in the following C/C++ sample.

Event function filtering communications events 

// The following event function will filter the modem event "RING"
// thus it will not get reported to the application.

   PUSEREVENTPROC pXEventProc=NULL;

   DWORD COMMAPI EventFilterProc (BYTE CommId, DWORD SComEvent)
   {
      DWORD Res=0;

      if (SComEvent & EV_RI)
      {
         SComEvent = ~EV_RI;  // clear bit
      }

       // If anything to report, call the previous event handler
       // All other events, while enabled, will reach the application

      if ( (SComEvent !=0 ) && (pXEventProc != NULL) )
         Res = pXEventProc (CommId, SComEvent);

      return (Res);
   }

// Setup:
// First we setup the new event handler and store the address of the
// previous event handler so we can call it when needed

   pXEventProc = ComGetSetEventProc(CommId, EventFilterProc);
     :
     :

This sample can be easily adopted to other development environments like Visual Basic, Delphi, C#, VB Net. SuperCom does also include support functions to overcome some compiler limitations regarding pointer and address calling functions.

 

[ Chart of Software and Features ]

Home    Back
Modified at:

ADONTEC