|
|
wodBeep
-
Version
1.0.0.0
ActiveX component is a peer-to-peer connection
convenient to label each peer to behave in context of
Listener(Server) or Initiator(Client). Component comes
with several profiles included such as: SINK/ECHO
profiles for testing, ROT13 profile that will grap
message data, ZIP Tuning profile that will compress
cocntents of messages on the fly, SYSLOG Raw and Cooked
profiles for transmitting (and recieving) syslog
messages....
BEEP protocol is a generic application protocol for
connection oriented, asynchronous interactions. It
permits simultaneous and independent exchanges within
the context of a single application user-identity.
It supports both textual and binary messages.
BEEP peers communicate with MESSAGES over predefined
CHANNELS. Messages are generated by application defined
PROFILES. Before message is sent, and once message is
recieved by the peer, Profile defines parsing to
provide necessary information.
MESSAGES
Messages are initiated by application, and are prepared
by defined Profile. Corresponding profile awaits on
other side to parse the message and provide only
necessary information.
CHANNELS
All exchanges occur in the context of a channel -- a
binding to a well-defined aspect of the application,
such as transport security, user authentication, or
data exchange.
PROFILES
Each channel has an associated "profile" that defines
the syntax and semantics of messages exchanged.
Implicit in the operation of BEEP is the notion of
channel management. Except for few profiles defined
internally in wodBeep you can define your own profiles:
for data exchange, tuning parameters etc...
TRANSPORT
A BEEP session is mapped onto an underlying transport
service. It can be single TCP connection, but also UDP
or any higher level two-way transport service-SMTP
arhitecture... wodBeep implements TCP transport for you
- you can implement easily any other transport just by
implementing IBeepTransport interface!!
|