ejabberd - Comments for "JEP-0009 Jabber-RPC Compatibilty"

RE: Well...

jfradley — Thu, 03 Aug 2006 18:57:03 +0000

Thanks for your help.

Well...

turner — Thu, 03 Aug 2006 18:27:52 +0000

We have three platforms that all have to talk Jabber-RPC. Each one took a different approach.

In Perl land we used POE::Component::Jabber for Jabber and RPC::XML to parse the Jabber-RPC payloads.

In Python land it's all written from scratch.

In Java land we used Smack for Jabber and rolled our own Jabber-RPC addon.

I'm not aware of any Jabber client APIs that support Jabber-RPC out of the box, but we found it pretty painless to add.

Great!

jfradley — Thu, 03 Aug 2006 15:16:33 +0000

Thanks for the reply. Are you guys using a particular client API? Would you suggest one that works well with Jabber-RPC?

Yes, it works

turner — Thu, 03 Aug 2006 15:13:59 +0000

Jabber-RPC doesn't require server cooperation. Over at http://volity.net we've been using ejabberd for quite a while now and our platform builds extensively off of JEP-0009. We haven't had any problem with any Jabber server. We've had users pass Jabber-RPC messages through ejabberd, jabberd 1.x, jabberd 2.x, wildfire, djabberd and google. (And quite possibly more, but those are the one's that I'm aware of.)