wodBeep - Version 1.0.0.0 ActiveX component is a peer-to-peer connectionconvenient to label each peer to behave in context ofListener(Server) or Initiator(Client). Component comeswith several profiles included such as: SINK/ECHOprofiles for testing, ROT13 profile that will grapmessage data, ZIP Tuning profile that will compresscocntents of messages on the fly, SYSLOG Raw and Cookedprofiles for transmitting (and recieving) syslogmessages....BEEP protocol is a generic application protocol forconnection oriented, asynchronous interactions. Itpermits simultaneous and independent exchanges withinthe context of a single application user-identity.It supports both textual and binary messages.BEEP peers communicate with MESSAGES over predefinedCHANNELS. Messages are generated by application definedPROFILES. Before message is sent, and once message isrecieved by the peer, Profile defines parsing toprovide necessary information.MESSAGESMessages are initiated by application, and are preparedby defined Profile. Corresponding profile awaits onother side to parse the message and provide onlynecessary information.CHANNELSAll exchanges occur in the context of a channel -- abinding to a well-defined aspect of the application,such as transport security, user authentication, ordata exchange.PROFILESEach channel has an associated "profile" that definesthe syntax and semantics of messages exchanged.Implicit in the operation of BEEP is the notion ofchannel management. Except for few profiles definedinternally in wodBeep you can define your own profiles:for data exchange, tuning parameters etc...TRANSPORTA BEEP session is mapped onto an underlying transportservice. It can be single TCP connection, but also UDPor any higher level two-way transport service-SMTParhitecture... wodBeep implements TCP transport for you- you can implement easily any other transport just byimplementing IBeepTransport interface!!