We'll agree that it was probably not the best solution. We need to find a better approach for this. One strong consideration is enhancing flags, allowing compression and doing compression at both the client and the server. That requires more help from the server folks. The other challenge here is that there is no standard JSON type and even if there were, we'd not likely want to key off of it.
To address this for now, maybe it'd be best to have a way to disable this behavior?
|
|
Agreed some kind of configuration would be great. As someone who is using the client with a standard memcached server I think ideally the default would be to compress everything but as long as it was configurable and documented it'd be a step in the right direction. I was going to look at making it a configuration option but can't get all of the unit tests to run, maybe I can try again if SPY-86 get resolved.
|
|
Lowering priority because this needs server side planning as well
|
Generated at Sun May 19 06:19:54 CDT 2013 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.