thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Lovell <>
Subject Re: Human Readable Protocols for python
Date Tue, 04 Aug 2009 12:51:40 GMT
I don't see a JSON protocol in the Python part of the source tree. In 
fact, the only languages, from my just browsing filenames in the source 
tree, that have JSON protocols are cpp and java. And I would rather 
stick with python or maybe perl.

I am not planning on using this for a regular protocol between 
applications. I am planning on this being used for a type of quick and 
dirty way for sys admins to be able to read and edit the configuration 
data that is in thrift. The apps that use this will just use the binary 



On 8/3/2009 9:00 AM, Bryan Duxbury wrote:
> You could use the JSON protocol, which is supported by many languages 
> and is very human readable. However, human readable protocols tend to 
> be bulky and slow, so be aware of the costs associated with that feature.
> On Aug 2, 2009, at 9:28 PM, Mike Lovell wrote:
>> First off, hello everyone.
>> I am new to Thrift and am experimenting with using it in an 
>> application I use. Currently, the data for the application is just 
>> stored in a text file with a read only python library wrapped around 
>> it. I am wanting something a little better and supporting multiple 
>> languages. So Thift is an intriguing technology.
>> But I am wondering, is there a python based protocol that is human 
>> readable? From looking at the source, it appears that the only 
>> protocol really available for python is the TBinaryProtocol (yes 
>> there is also TBinaryProtocolAccelerated). I am wanting something 
>> that is human readable and able to both read and write objects to and 
>> from the file. Having this would make changing to a Thrift based data 
>> store a lot easier to sell to my co-workers. I am thinking of writing 
>> one but I am not a great programmer and would definitely like to 
>> build on what someone else has already done.
>> Thanks in advance.
>> mike

View raw message