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.
WeOnlyDo!COM will be the first stop I make should I require any further off-the-shelf components.
Fantastic product by the way, it has helped us tremendously on a daily basis. Keep up the good work.
May I say how nice it is to work with components so complete and self-explanatory that using them in my application is as instinctive as though I wrote them myself?
...wodFtpDlx was exactly what I needed, it worked, and it was priced right...
Thank you so much for your hard work and commitment in producing well thought-out solutions. WeOnlyDo is very committed to customer satisfaction!
Thank you for the great customer service ... I am really impressed with the wodSSH ActiveX control.
Your .NET components allow us to blend .NET technology seamlessly with secure communication, and with excellent technical support.
...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...
Your support is fantastic.
This has been, by far, the best experience I have ever had dealing with a support entity in my long career in the technical arena