Hi all, Looking at the wire format's type IDs, it's clear that thrift supports several thrift encodings in it's wire format, yet the IDL does not allow one to speak of string encoding (string/binary are the only type names in the IDL).
Is this a design decision (where each language implementation can choose the appropriate Unicode type id for encoding strings), or is there some historical reason for not exposing string encoding options in the thrift IDL? Thanks, Peter -- *Peter Neumark* DevOps guy @Prezi <http://prezi.com>
