views:

40

answers:

1

I am tasked with creating a text messaging system with low bandwidth server to server connections. The other developers already use protobuf to send data for other parts of the system between these same server locations, and it would be helpful to continue that trend for the text messaging portion. Server to client connections are not bandwidth constrained. It would be great to be able to use an unmodified chat client and openfire xmpp server.

What is better to program in this situation, a component for openfire or a transport for Kraken?

A: 

Have you tried enabling XEP-138 compression on the server-to-server link? Even if OpenFire doesn't support XEP-138, it will be easy to add, and should provide better results that almost any naive translation to protobufs.

Joe Hildebrand
If this is compressing xml, won't it still be larger than a protobuf message? The decision makers on this project really want the smallest data transmissions possible.
This can only be proven with data on *your* expected data stream, but I think you'll be **shocked** how well the XML compresses. Compressed XML will likely beat uncompressed protobufs by a good amount, at the cost of higher CPU on either side, but with the advantage of extensibility.
Joe Hildebrand

related questions