Custom Application
Description - Stand-alone,
application-level program
Purpose - Developers create a
custom application:
- To process encapsulated payload data only - The custom application:
- Opens a connection(s)
to Gcom_pcd.
- Exchanges messages with Gcom_pcd that consist of an encapsulation header and payload data.
- Or to process encapsulated payload data and/or legacy connection management messages - The custom application:
- Opens a connection(s)
to Gcom_ssd.
- Exchanges messages with
Gcom_ssd that consist of a SyncSockets
API header (message-handling instructions)
and possibly data.
- Manages the state of legacy
protocols by tracking the status
of the SyncSockets Finite State Machine
(which detects illegal operation sequences
as well as returns simple codes that
tell the custom application
what to do next).
Development Prerequisites - A
developer:
- Must understand TCP/IP protocol and
sockets programming.
- Need not understand legacy
protocols or legacy
APIs because the custom
application:
- Does not interact directly
with the underlying legacy protocol
stack drivers.
- Interacts instead with Gcom_pcd via the Gcom Data Tunneling API, or Gcom_ssd
via the Gcom SyncSockets API. And both the Data Tunneling API and SyncSockets API are built on top of
sockets to give them a TCP/IP-based
look and feel.
|
|
For more information...
|
|
