Right now the "string" type in Apache Thrift is abstract. I like that. If
you are using Java or C# then Apache Thrift strings are UTF-16. If you are
using Python or Go, then Apache Thrift strings are UTF-8. So the protocols
are already serializing between the language native string type and UTF-8
o
I don't like the idea of adding a new utf-16 string type to the wire
protocol, but I think it would be fine to add a utf-16 string type to the
language bindings. UTF-8 would be sent over the wire, and then converted
from the network buffer into the user's desired string type. A lot of the
cost an
[
https://issues.apache.org/jira/browse/THRIFT-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
phoneli updated THRIFT-3513:
Description:
In Source Code " lib/cpp/src/thrift/TToString.h " ,
lines between 34~37 :
template
[
https://issues.apache.org/jira/browse/THRIFT-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
phoneli updated THRIFT-3513:
Description:
In Source Code " lib/cpp/src/thrift/TToString.h " ,
lines between 34~37 :
template
[
https://issues.apache.org/jira/browse/THRIFT-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
phoneli updated THRIFT-3513:
Description:
In Source Code " lib/cpp/src/thrift/TToString.h " ,
lines between 34~37 :
template
phoneli created THRIFT-3513:
---
Summary: lib/cpp/src/thrift/TToString.h : the function "to_string"
is not compatible for int8_t(byte)
Key: THRIFT-3513
URL: https://issues.apache.org/jira/browse/THRIFT-3513
Pr
Yes, that was the question. It could eliminate some conversions from and to
utf8 (speed is a Thrift goal) but I'm not sure if the possible gains are worth
doing it.
Re keeping it simple: I fully agree, absolutely. But we have 4 integer types
and there are thoughts to integrate floats as well ..
