[jdev] Mil XMPP to replace SOAP?

Jones Alasdair AJONES5 at mail.dstl.gov.uk
Thu Apr 14 09:25:34 CDT 2005


Alasdair Jones
ajones5 at dstl.gov.uk <mailto:ajones5 at dstl.gov.uk> 
Office: +44 (02392) 217663
Lab:    +44 (02392) 217488
Fax:    +44 (02392) 217535

> -----Original Message-----
> From: Fabio Forno [mailto:fabio.forno at polito.it]
> Sent: 14 April 2005 15:03
> To: Jabber software development list
> Subject: Re: [jdev] Mil XMPP to replace SOAP?
> Jones Alasdair wrote:
> > If I use XMPP I will be ditching SOAP. The data is all XML, 
> so it could be
> > put straight into the XMPP message.
> Which is equivalent to document-style SOAP messages when you 
> do not need 
> all the extra features of SOAP headers (addressing, logging, security 
> etc) ;)
> > I mentioned speed, because I have had experience using the 
> Jabberd sever and
> > my clients (using MUSE API) with a large number of (small) 
> messages and it
> > seemed to queue them up and send them in batches. In some 
> cases, messages
> > took about a minute to arrive which is not good enough.
> Was the sender a client or compoment? Jabberd does traffic 
> shaping for 
> clients and the feature is configurable

Senders were clients. So your saying that this is totally avoidable with a
few config changes?

> > Any comments about security. What is the support for this 
> in XMPP? It would
> > be preferable to have multiple security layers to allow 
> clients to specify
> > which other clients have access to their data.
> The logic of pubsub subscriptions, where node visibility is 
> configurable 
> will work, then if you want to protect messages from sniffing you can 
> use TLS connections or pgp on each message, servers support them
> -- 
> Fabio Forno, Ph.D.
> *** Employer line for sale ***
> Phone: +39 011 2276 102 - JabberId: sciasbat at jabber.linux.it
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mail.jabber.org/mailman/listinfo/jdev

"This e-mail is intended for the recipient only.  If you are not the
intended recipient you must not use, disclose, distribute, copy, print,
or rely upon this e-mail. If an addressing or transmission error has
misdirected this e-mail, please notify the author by replying to this e-mail."

"Recipients should note that all e-mail traffic on MOD systems is
subject to monitoring and auditing."

More information about the JDev mailing list