SuperCom™ TCP/IP

---

The Communication Toolkit for TCP/IP in
Windows 7, Windows Vista, Windows Server 2008, Windows XP, Windows Server 2003, Windows 2000, Windows NT, Windows ME/98/95

Communication Solutions by ADONTEC SuperCom Suite DEMO (Serial, ISDN, TCP/IP)

Version 7 Price List Product Range Call Me Back

Looking for ZMODEM over TCP/IP ?

The SuperCom for TCP/IP communication library handles data communication over TCP/IP networks (internet and intranet).

The SuperCom for TCP/IP communication library provides an optimized Data Communication Engine, which handles concurrent connections, buffers data and generates events. This Data Communication Engine provides maximum functionality but reduces CPU load and resource consumtion to a minimum. The Data Communication Engine can also continuously update the application by triggering events. Unwanted events can be disabled thus reducing overhead.

Portable API
The easy to use and portable SuperCom API enables fast implementation of TCP/IP applications. A client or server application can be build in short time. Setting up connections and file transfer using standard protocols like ZMODEM is easily done. The event reporting mechanism and the background operation of most SuperCom functions generate a fast responsive and rock solid application.

Anyone that worked with Window's sockets or some other third party library, knows how difficult this task can sometimes be. However, thanks to the SuperCom API, establishing many client connections or making server applications is a lot easier than it's used to be. And best of all: the whole data communication, even file transfer is completing transparently in background - that's standard when using any SuperCom!

A single application using SuperCom can run up to 255 connections simultaneously. Nearly any combination possible, for example 1 server that accepts up to 254 connections or up to 255 client connections to remote server or any other combination of client and server up to 255 connections per application.

Portable Protocols
The SuperCom functions and protocols are also available over TCP/IP e.g. ZMODEM, YMODEM, XMODEM, XMODEM-1K, KERMIT, Extended XMODEM, ASCII, 3964/R, RK512, MODBUS and LSV/2 (for the use of the 3964/R and/or LSV/2 protocol the SuperCom 3964/R Protocol Engine and/or the LSV/2 Protocol Module is also needed).
The SuperCom ZMODEM implementation also includes special options for slow communication channels (high latency connections e.g. satelites or wireless).

The use of the common SuperCom API enables a move from RS-232 to TCP/IP or from ISDN to TCP/IP to be very smooth and quick. Using the SuperCom Suite enables one single application to handle simultaneously connections through Serial, TCP/IP and ISDN. The SuperCom Suite offers even more samples for TCP/IP communications.

Start fast
Many complete real world samples (client and server) for TCP/IP applications are included in source code and for many developing environments and compilers.

Sharing TCP/IP connections
SuperCom can (in most cases) use connections established by a third party library. Using a SuperCom TCP/IP connection with a third party libraries is usually possible. If you need to share a connection, please describe your environment in detail to confirm functionality.

Small Footprint
Contrary to other libraries and development environments, the SuperCom for TCP/IP was designed and well optimized especially for harsh environments and it therefore consumes relatively low resources and utilizes low CPU. This operating characteristics also result to a fast responsive and rock solid application. You don't need to limit your application to run on high-end machines only!

Features & Functions List
A DUAL API programming interface is included (DLL API and ActiveX API) .

DLL API	ActiveX API
Features	Features
Functions	Properties

The box includes
 - SuperCom DUAL API for Windows
 - ActiveX and DLL Samples
 - Documentation

Samples
Many TCP/IP Server and Client samples are included in source code for popular compiler incl. C/C++, C#, Visual Basic .net, Visual C++, Visual Basic, Borland C/C++, C++ Builder, Delphi, VBA, LabView, FoxPro.
Real world high-speed and high-load TCP/IP Server applications written in C/C++, C#, VB Net, Delphi included.
Read more about one of the real world TCP/IP Client / Server projects included (ServerClient.pdf). Similar sample projects are also available for C#, VB Net, Delphi, C++, Visual Basic.

A short list of C# & VB Net samples.

Some pictures from SuperCom samples.

See also the the available product range for details.

Read more about the Serial to TCP/IP GateWay software (COMMServer, PortServer) developed with SuperCom.

Supported Compilers
C#, C++, Visual Basic NET, Visual C++, Visual Basic, Borland C/C++, C++ Builder, Delphi, VBA, LabView, FoxPro and DLL and/or ActiveX capable Windows developing environments (.NET ?).

License Information
Executables developed using SuperCom can be distributed royalty free.

Requirements
Windows 7, Windows Server 2008 R2, Windows Server 2008, Vista, Windows XP, Windows Server 2003, Windows 2000, Windows NT, Windows 9.x/Me.

Sample - Connecting

Spending some time with the following sample shows how easy it is to use the SuperCom API. To make the use of SuperCom the same easy as possible within (nearly) any common IDE or programming language was an ultimate goal of our engineers.

DLL API
In order to receive events the application must provide an InfoProc*. The InfoProc is optional but very handy in many situation. Using the InfoProc the application can receive progress information, get informed about the time left to complete a call or even cancel the connection attempt.

   int InfoProc(Com, Action, TimeLeft, Data)
   {
      if (Action==acCONNECT_INFO)
      {
         // Received periodically, while in progress
      }
      if (Action==acCONNECT_OK)
      {
         // Connected !
      }
      if (Action==acCONNECT_FAILED)
      {
         // A connection attempt failed
      }

      return infContinue;

   }
      :
      :
     // init  ...
   ComInit(Com);

     // now connect ...
   Res = RS_ConnectEx(Com, SEC_60, , "www.adontec.com:80",InfoProc);

   Public Function InfoProc(ByVal Com As Byte, _
                            ByVal Action As Integer, _
                            ByVal TimeLeft As Long, _
                            ByVal Data As Long) As Long

      If SComAction = acCONNECT_INFO  Then
         'Received periodically, while in progress
      End If
      If SComAction = acCONNECT_OK  Then
         ' Connected !
      End If
      If SComAction = acCONNECT_FAILED Then
         ' A connection attempt failed
      End If

      InfoProc = infContinue

   End Function
        :
        :
     ' init  ...
   Call ComInit(Com)

     ' now connect ...
   Res = RS_ConnectEx(Com, SEC_60, , "www.adontec.com:80", InfoProc)

   Function InfoProc (Com:Byte; Action:WORD; TimeLeft:TDWORD; Data:PFDATA):Integer;
   Begin
      InfoProc:=infCONTINUE; { Continue }

      If (Action = acCONNECT_INFO) Then
      Begin
         // Received periodically, while in progress
      End;
      If (Action = acCONNECT_OK) Then
      Begin
        // Connected !
      End;
      If (Action = acCONNECT_FAILED) Then
      Begin
        // A connection attempt failed
      End;
        :
   End;
      :
      :
     // init  ...
   ComInit(Com);

     // now connect ...
   Res = RS_ConnectEx(Com, SEC_60, , 'www.adontec.com:80', @InfoProc);

   public int InfoProc(int Com, short Action, int Data, int pNotUsed)
   {
      switch (Action)
      {
         case SuperCom.acCONNECT_INFO:
               // Received periodically, while in progress
              break;
         case SuperCom.acCONNECT_FAILED:
               // A connection attempt failed
              break;
         case SuperCom.acCONNECT_OK:
               // Connected !
              break;
         case SuperCom.acUSERBREAK:
              // break by user
              break;
      }
      return SuperCom.infCONTINUE;
   }
      :
     // init  ...
   SuperCom.ComInit(Com);

     // now connect ...
   Res = SuperCom.RS_ConnectEx(Com,SuperCom.SEC_10,,"www.adontec.com:80",cbConnectInfoFunc);

The connection set-up can run completely in background. The application receives events about the progress.

Want to compare the above code with the one used for serial modem connections or ISDN to see what is different?

ActiveX API

  Private Sub SCom1_OnConnect(ByVal Action As Integer, ByVal TimeLeft As Long)

     If Action = SCOM_CONNECT_FAILED Then
       Form4.CTL_INFO.Text = "CONNECT FAILED"
     End If
               ' successfully
    If Action = SCOM_CONNECT_OK Then
      Debug.Print "CONNECTED ";
    End If
               ' progress...
    If Action = SCOM_CONNECT_INFO Then
      Debug.Print ".";
    End If

  End Sub

      :
      :

  SCom1.PortOpen=True ' setup a link
      :
  SCom1.ConnectAddress="www.adontec.com:80"  ' server address and port
      :
  SCom1.Connect=True ' now connect

      :

Setting up a TCP/IP connection runs completely in background. The application receives events about the progress.

The same sample for Serial or ISDN ?.

No matter what communication type in use (Serial, TCP/IP or ISDN) it requires only one common SuperCom API to use. The learning curve is extremely low with SuperCom!