-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Henrik Størner wrote:
It requires a new hobbitd daemon on the server side, and a new "bb" utility at the client. Compression is not turned on by default - you'll have to invoke "bb" as "bbz", or pass it the "--compress" option.
Sorry to continue this conversation, but I'd like to clarify some implementation details.
If I have two hobbit servers, and one bbproxy server which transmits the data to both hobbit servers, and of course multiple bb clients behind the bbproxy.
Do I need to update *both* hobbit servers, or could I only upgrade one hobbit server, and the bbproxy, and bbproxy would be capable of compressing received updates, and forwarding them to the compression capable server, and forwarding the uncompressed updates to the older server?
Also, how do old hobbit clients, or bb windows clients, or hobbit windows clients behave when behind the bbproxy? Would I need to upgrade each client for it's updates to be compressed, or will bbproxy handle that for me?
Thanks, Adam
Adam Goryachev Website Managers www.websitemanagers.com.au -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklIekYACgkQGyoxogrTyiUI6gCfV3QJ0IhoA/ejrA6eBxkFGwy0 LfsAn2xIol3ngZh7IzrH7GtpDGblv9Nb =XXSK -----END PGP SIGNATURE-----