john-->myserver.org-->hisserver.org-->fred
Now if we look at what happens when a message is sent: john-->compress-->myserver.org-->decompress-->interpret--> compress-->hisserver.org-->decompress-->interpret-->compress--> fred-->decompress As opposed to (with e2e compression): john-->compress-->myserver.org-->interpret-->hisserver.org--> interpret-->fred-->decompress Obviously only the payload would be compressed, the stanza wouldneed to stay intact. Much simpler algorithms could then be used on the servers that explicitly deal with compressing XML efficiently.
I know this has the potential to be a terrible idea... Regards, Jonathan Dickinson -- jonathan chayce dickinson ruby/c# developer email: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] <some profound piece of wisdom>
smime.p7s
Description: S/MIME Cryptographic Signature
