[an error occurred while processing this directive]
Location: > Products > 4D Components > TCP Deux > Features    Site Map
[an error occurred while processing this directive]

Features in the TCP Deux component

With the TCP Deux component, a 4th Dimension developer can code TCP level routines without worrying about which particular plugin is going to be used. TCP Deux provides a very simple upgrade path for developers to write one set of code. With TCP Deux, a 4D developer can begin by using the free 4D Internet Commands for all TCP communications and upgrade to the commercial Internet ToolKit plugin when the needs arises, all without changing a single line of code.

At its core, the TCP Deux component provides a wrapper layer for all major TCP plugins available for 4th Dimension. This wrapper layer provides seemless development, integration, and switching between different TCP plugins popularly used in 4D. The TCP Deux component thereby provides a single set of commands for access any TCP layer functionality and is the basis for all other higher level protocol components (e.g. SMTP Client Deux, FTP Client Deux, HTTP Client Deux, HTTP Server Deux, etc.).

TCP Deux is compatible with both 4D v6.7.x, 4D v6.8.x, and 4D v7.0.x (4D 2003). This means there is complete compatibility for all available platforms 4D is currently available on. As well, TCP Deux is fully backwards compatible with all versions of the different TCP plugins available for both of these versions of 4D.

So, with TCP Deux, any of the following TCP plugins can be used for compatibility:

  • 4D Internet Commands v6.7.x (with 4D v6.7.x only);
  • 4D Internet Commands v6.8.x (with 4D v6.8.x only);
  • 4D Internet Commands v7.0.x (with 4D v7.0.x [4D 2003] only);
  • Internet ToolKit v2.0.x (with 4D v6.7.x only);
  • Internet ToolKit v2.5.x (with 4D v6.7.x, 4D v6.8.x, and 4D v7.0.x [2003]);

All platforms, including MacOS v8.x, MacOS v9.x, MacOS X, and Windows 95/98/2000/NT/XP can be used for development and deployment with the TCP Deux component.

TCP Deux supports running in demo mode. Demo mode allows for the component to be fully used for 30 minutes when no serial code is supplied to the TCP Deux component.

A full manual, explaining every call and feature available in TCP Deux, is included with the component.

TCP Deux provides cross-platform, plugin independent routines for handling all TCP communications in 4D. The functionality available in the TCP Deux component include:

  • Stream and listener openers and closers;
  • Stream status checking, individually or for all open streams;
  • Processor friendly stream status waiting routines;
  • Full support for sending and receiving text and binary data;
  • Full support for sending and receiving directly from documents;
  • Full management system for TCP communication streams;
  • Full multiple 4D process (handler) support for TCP servers;
  • Accessor methods for updating and extracting stream information;
  • Accessor methods detailing TCP environment on local machine;
  • Transparent support for IC v6.7.x, IC v6.8.x, IC v7.0.x (2003), ITK v2.0.x, and ITK v2.5.x;
  • Full SSL support when using ITK v2.5.x or IC v6.8.1 and above;
  • Compatibility with 4D v6.7.x and above;
  • Full support for MacOS 8/9, MacOS X, and Windows 98/2000/NT/XP.

The TCP stream management system, entitled TCPd Streams Stack, built into TCP Deux provides a complete management and tracking system for 4D developers to use for handling all TCP streams. The TCPd Streams Stack provides transparent management of all TCP streams, allowing the 4D developer to concentrate on management the higher level TCP protocol being coded for instead of the direct management of the TCP connection streams. And, the TCPd Streams Stack even provides full support for common TCP serving options (e.g. distributed process handlers within 4D).

The TCP Deux component requires the BASh component be installed to operate properly. BASh is available for free from Deep Sky Technologies, Inc., and provides essential routines needed by all 4D programmers.

[an error occurred while processing this directive]