On Dec 3, 2009, at 9:13 PM, Markus Roberts wrote:
>> Even this selective loading isn't a complete solution, though, is it?
>> What if the client side of the connection has zlib and the server
>> doesn't?
>
> Our conclusion on the compromise had been that you had to have zlib on
> the server if you were going to have it on any of the clients--the
> reason being that it seemed much more reasonable for someone to say "I
> run my clients very light weight, and don't want zlib on them" than it
> was for someone to say "I want to have zlib on my clients but refuse
> to have it on the server."
I agree with that decision, but how do we handle usability? Does the
server have a reasonable exception for telling the user this?
And, somewhat more importantly, does the server recognize that it was
passed compressed text but it has no way to decompress it?
I guess that's why it's using a separate format -- if it doesn't
support that format, then it behaves appropriately.
As long as the user on the server gets an error somewhere that says
"hey, the client's using zlib but the server doesn't have it", I'm good.
--
The most dangerous strategy is to jump a chasm in two leaps.
-- Benjamin Disraeli
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
