[jdev] Financial messaging via XMPP

[Richard Dobson]

> 1. Size of XMPP wrapper of the binary message - 360 bytes in the 
> example in the article - with financial protocol like FIX/FAST the 
> binary data tend to be quite small (30-40 bytes) thus 360 bytes of 
> wrapping XML can extend the message size tenfold.
Compression will solve much of this.
>
> 2. Compression and decompression (binary->base64->TLS compression->TLS 
> decompression->base64->binary data) may cause latency to be worse. 
> However, I am not sure what exactly the impact would be.
Base64 is trivial to compute and as far as TLS is concerned surely being 
financial information you would be required to have it encrypted? The 
encryption rather than the compression part is likely to be the most CPU 
intensive part.

Richard