Jones Alasdair wrote:
Senders were clients. So your saying that this is totally avoidable with a
few config changes?
Yep, read the karma settings section of the jabber config file; a better
solution would be to implement the node generating huge traffic has
components, which don't have those rest
e 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
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
Thanks for your help, I'll take a look at the archives.
If I use XMPP I will be ditching SOAP. The data is all XML, so it could be
put straight into the XMPP message.
I mentioned speed, because I have had experience using the Jabberd sever and
my clients (using MUSE API) with a large number of (s
