[
https://issues.apache.org/jira/browse/THRIFT-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624242#action_12624242
]
Noble Paul commented on THRIFT-110:
-----------------------------------
bq.Not directly related and I don't know if this is possible. but it would be
pretty interesting if thrift could "speak" protocol buffers - i.e., if we had
TProtocolBuffersProtocol.
When it comes to binary protocols interoperability is not a very nice thing to
have. We will have to keep a close track of how the other protocol is making
use of certain 'bits' and we will have to resort to very clever tricks to work
around. Thrift in itself can become a standard and anyone who wants to use both
thrift and some other protocol (say protobuf) can have two separate output
formats.
> A more compact format
> ----------------------
>
> Key: THRIFT-110
> URL: https://issues.apache.org/jira/browse/THRIFT-110
> Project: Thrift
> Issue Type: Improvement
> Reporter: Noble Paul
>
> Thrift is not very compact in writing out data as (say protobuf) . It does
> not have the concept of variable length integers and various other
> optimizations possible . In Solr we use a lot of such optimizations to make a
> very compact payload. Thrift has a lot common with that format.
> It is all done in a single class
> http://svn.apache.org/viewvc/lucene/solr/trunk/src/java/org/apache/solr/common/util/NamedListCodec.java?revision=685640&view=markup
> The other optimizations include writing type/value in same byte, very fast
> writes of Strings, externalizable strings etc
> We could use a thrift format for non-java clients and I would like to see it
> as compact as the current java version
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
