Github user jeroenvlek commented on the pull request:
https://github.com/apache/thrift/pull/213#issuecomment-114746082
I'd be happy to make a new pull request with the adapted writeString and
readString, but do you want to have the assumption that the incoming string is
either encoded with UTF-8 or a bytestring hard-coded?
Maybe you could keep writeString for byte strings and create a writeUtf8?
---
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.
---
