|
To transport and to warrant good delivery of application data/messages while using tcp/ip sockets or named pipes, the
component ScriptEZ.API provides two managed mechanisms and one free way: ·
Simple and understandable algorithm This default and first encapsulation relies on a simple
zero-left-padding 10 characters header which contains the length of a
message, and is followed by the real data/message payload itself (<10 bytes zero-left-padding hdr><Payload>). This header’s
length can accordingly be ranged beyond or beneath the purposed default
length (10 bytes) with ChangeIPCMessageHeaderSize(…) ·
Encryption and privacy algorithm Secondly, when
calling EnableSocketObjectDataEncryption() or EnableNamedPipeObjectDataEncryption(),
the component will apply an undisclosed algorithm which encrypts
data/messages before sending them into a socket or a named pipe stream. Be
aware that this mechanism involves necessarily to develop
both peers applications (clients and server) with the ScriptEZ.API object. ·
Free and harder The third way relies on call of EnableSocketObjectFreeMessageUsage(…), which
will let data/messages stream flow thru raw
tcp/ip sockets. Be aware that “free message usage” mechanism involves
more endeavour from packaging and unpackaging
application data/messages. Those
tasks will be on your own in order to warrant properly a good
delivery of data/messages. Use this method, if you have no choice or
you only want to try/rely on automatic
reconnection feature and other facility methods/properties for sending/receiving
data/messages from a remote and foreign tcp/ip server application with
its own communication protocol (or
its communication specifications) |