Using Delphi to establish communication and data Exchange Server-transceiver Technical Analysis (i)

Introduction

In the domestic common information development and implementation projects, most of the work of the development of the workload is concentrated in order to adapt to different customer needs, the specific modules to modify, and ultimately achieve customer expectations of the software functional characteristics. But for the development of vendors, in the face of different customers to develop different software versions, will lead to duplication of labor, cost rise, maintenance increase, compatibility and decline in stability and other issues. Therefore, developers realize that the realization of software products, to have a shorter project cycle and strong market competitiveness, as much as possible to adapt to the needs of different customers, and will not be so bogged down, is the customer satisfaction and business interests of a balance point.

Transceiver Concept

Transceiver is a universal communication product software designed to meet the diverse communication needs of different applications and business projects. It is designed to reduce the repetitive development of communication modules and to enhance the centralized management of communication software, which can be used for platform neutral application neutral unified control communication and data exchange between multiple application systems. By abstracting send and receive (receive) as an equivalent data flow process from source to host (Target), the integration of the existing common methods of communication and the processing of fault-tolerant buffering (Queue) for communication anomalies constitutes Transceiver is powerful enough to meet the needs of enterprise-class communications.

The following are examples of transceiver applications

Communication direction	Sources (source)	Buffer (Queue)	Trust Bed (Target)	Implementation features
C1. Sending data	S1. Obtained from local file	If there is an anomaly, the data can be buffered in the transceiver, and the transceiver is responsible for the postback.	T1. Commit to remote TCP port	Transferring files to the remote
C2. Receive data	S2. Obtained from distal POP3	T2. Submit to another SMTP account	Mail forwarding
C3. Sending data	S3. Obtained from local db	T3. Submit to Remote HTTP page	Read from a database and submit to a Web page
C4. Receive data	S4. Obtained from remote FTP	T4. Commit to local COM for processing	Get from the remote and submit to COM processing
C5. Receive data	S5. Obtained from remote DCOM	T5. Commit to local MSMQ queue	Get stored in message queue from remote component for processing

Both the transceiver Citic Source (source) and the host (Target) are treated as ports (port), such as S1~S5, T1 ~t5, which are all communication components created and controlled by transceiver at run time, and several traffic similar to C1~C5 A process definition is considered a channel (Channel), and a Channel that can complete basic communication functions consists of two port components (one Source, one target), and the queue is a fault-tolerant processing layer for communication anomalies. As shown in the table, transceiver can provide full support for sending/receiving two class communication processes. And the type, quantity and relation of the source and the host are not limited, and the matching relationship between source and target can be set freely.

The above table just enumerates a few use cases of transceiver communication function, transceiver abstraction integrates the data communication elements of the application, data and protocol three levels, can adapt to the complex and changeable communication demand, The communication requirements of the application provide maximum flexibility and reusability. Figure 1:transceiver Communication ports (port) interactive capabilities