The existence of the "binary" type is now documented in the relevant places.
git-svn-id: https://svn.apache.org/repos/asf/incubator/thrift/trunk@739702
13f79535-47bb-0310-9956-
ffa450edef68
<field-name> ::= STRING
<field-type> ::= T_BOOL | T_BYTE | T_I8 | T_I16 | T_I32 | T_I64 | T_DOUBLE
- | T_STRING | T_STRUCT | T_MAP | T_SET | T_LIST
+ | T_STRING | T_BINARY | T_STRUCT | T_MAP | T_SET | T_LIST
<field-id> ::= I16
- <field-data> ::= I8 | I16 | I32 | I64 | DOUBLE | STRING |
+ <field-data> ::= I8 | I16 | I32 | I64 | DOUBLE | STRING | BINARY
<struct> | <map> | <list> | <set>
<map> ::= <map-begin> <field-datum>* <map-end>
\item \texttt{i64} A 64-bit signed integer
\item \texttt{double} A 64-bit floating point number
\item \texttt{string} An encoding-agnostic text or binary string
+\item \texttt{binary} A byte array representation for blobs
\end{itemize}
Of particular note is the absence of unsigned integer types. Because these
* i64 Signed 64-bit integer
* double 64-bit floating point value
* string String
+ * binary Blob (byte array)
* map<t1,t2> Map from one type to another
* list<t1> Ordered list of one type
* set<t1> Set of unique elements of one type