Description from the publisher
Basic information about wodXMPP
You can use wodXMPP as instant messaging and presence protocol - you can see your contacts online, send and receive messages with them, send and receive notifications, etc.
There are two variations of wodXMPP -
1. COM Object which is invisible and should be used "under the hood" in your applications
2. OCX Control which has GUI (as seen on the right side of this page). Each contact is drawn by wodXMPP itself so you don't need to create your own code to show contacts on the screen. No code is required to have visible contact list on the screen.
Main wodXMPP object is responsible for you as an entity on the Jabber network. You can find here methods to connect and disconnect, to set your JID, password, etc..
Your buddies are called 'Contacts' and are provided through XMPPContact object. Here you can add them to your contact list, send authorization requests, send messages... Messages are created in separate XMPPMessage objects where you can set up all details of messages.
There are dozen of objects in wodXMPP component that parse incoming data to separate standalone entities which you can easily use and manipulate in your code.
Sending and receiving messages
It is easy to send message with wodXMPP - you can do it from one line using SendText method. If you need to construct more complicated messages, you can initialize included XMPPMessage object, supply few properties, and then call SendMessage method to deliver it to your contact.
Connecting to other protocols
wodXMPP supports (if your server provides it) connecting to other instant messaging protocols - such as ICQ, MSN, AIM, Yahoo, GTalk etc..
You can feel safe with wodXMPP - no one will see messages you send because wodXMPP uses SSL. Both Explicit and Implicit modes are provided, so you can connect to regular port 5222 and then "fire up armor", or you can connect to port 443 to services that have SSL enabled.
Other products of this publisher
Secure FTP client .NET 2.0 component that supports encrypted and non-encrypted FTP access to the servers for transferring files or complete directories. It supports old, very common, FTP protocol, but also secured FTPS (FTP+SSL) and SFTP (FTP+SSH).
Lightweight component that provides strong encryption for your applications. It provides supports for most common crypto algorithms, such as:AES, DES, TripleDES, Blowfish, Cast, RC2, RC, RC5, etc...
Developers are able to add 'update over the web' functionality to your software with a single line of code. WodAppUpdate allows developers an easy way to deploy their updates on the host site and let users download them in just a few secounds.
Secure FTP client ActiveX component th It supports old, very common, FTP protocol, but also secured FTPS (FTP+SSL) and SFTP (FTP+SSH). It supports old, very common, FTP protocol, but also secured FTPS (FTP+SSL) and SFTP (FTP+SSH).
WeOnlyDo! SmtpServer ActiveX control is a component that can be easily integrated into your applications to provide full non-relaying Smtp (Simple Mail Transfer Protocol) server implementation
ActiveX client component used to deliver e-mail messages directly to the server of the recipient, using SMTP protocol. It automatically finds appropriate server where message should be delivered,or uses SmartHost through Hostname property.
wodVPN is VPN peer-to-peer ActiveX component that is used to establish Virtual Private Network between two peers. All P2P communication is encrypted and secured. Peers are able to forward local and remote ports, send messages, etc.
wodTelnetDLX a telnet client component ready to connect to terminal based clients,most commonly to UNIX telnet daemon. It also supports secured communication (through encryption) using well known SSH (SS1&SSH2) and SSL/TLS
ActiveX Component that implements server side of HTTP and HTTPS protocols (HTTPServer). It's main purpose is to serve HTML pages, GIF/JPG/PNG images, documents, and other resources that are accessible through Browser clients.
The Secure File Transfer Protocol provides secure file transfer functionality over any reliable data stream, SSH in this case. It is the standard file transfer protocol for use with the SSH2 protocol.