Github user adam-aph commented on the pull request:
https://github.com/apache/thrift/pull/81#issuecomment-38957593
Hi Henrique - I think this new parameter would be required - the patch is
not breaking existing code, however it may reveal issues in existing
applications (currently the deserialization delivers always newly allocated
objects, but when the re-use is switched on, the application needs to remember
to properly "clean" all storage objects, otherwise subsequent deserializations
will be added on the top of previous ones.
So I think enabling this feature by default for all applications may create
headache.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
