wodXMPP is a client component for XMPP/Jabber (Extensible Messaging and Presence Protocol) protocol. It is used to create messaging clients that are lightweight and need no other 3rd party requirements than 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..
our 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.
wodXMPP supports (if your server provides it) connecting to other instant messaging protocols - such as ICQ, MSN, AIM, Yahoo, GTalk etc.. You need to Discover services supported on the server, and register yourself with one (or more of them). After that, talking with your buddies on those networks is just the same for you as they are using wodXMPP too.
File transfers are supported too, and tested with most other XMPP/Jabber clients. Several technologies are supported, so if one of them fail wodXMPP will automatically fail over to older standard.
There is even internal HTTP server that can serve your files to remote contacts.
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 implicitly expect to have SSL enabled (such as GTalk service). wodXMPP will play nicely with them.
Thanks! We love your software and your great support!
Just thought you'd like to know that my gateway app with your SMTP Server component held the line against a DDOS attack today...
We are having great success with your component ... email server that has over 750 000 mailboxes back ended by a SQL server...
The SFTP ocx is one of the finest pieces of programming I have seen. It worked out of the box...
...with a minimum of effort as the DLL interface was written with such simplicity...
...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...
...with WOD's excellent support I was able to bypass Winsock and focus on the task at hand...
You have been great as far as offering support is concerned and has been extremely responsive to both support requests and suggestions for product enhancements.
Thank you for the great customer service ... I am really impressed with the wodSSH ActiveX control.
...with the SFTP interface you produced, everything was so simple to understand, we were able to start coding almost immediately!