example - codepad

Python, pasted 23 minutes ago:

I have not compared them in deiatl myself, but if you believe Google's description of Protocol Buffers, it's primary feature is one you have not included in your consideration. They claim that their binary format is (1) especially small and (2) especially quick to serialize and deserialize. I am not particularly familiar with Thrift, but I never had the impression that these particular optimizations were of great importance to that project. The Google version is optimized for the case where you are dealing with truly massive amounts of data (the RARE case where efficiency trumps readability).  Michael Chermside

view (1 line, 4 lines of output)

Python, pasted 23 minutes ago:

I have not compared them in deiatl myself, but if you believe Google's description of Protocol Buffers, it's primary feature is one you have not included in your consideration. They claim that their binary format is (1) especially small and (2) especially quick to serialize and deserialize. I am not particularly familiar with Thrift, but I never had the impression that these particular optimizations were of great importance to that project. The Google version is optimized for the case where you are dealing with truly massive amounts of data (the RARE case where efficiency trumps readability).  Michael Chermside

view (1 line, 4 lines of output)

Python, pasted 1 hour ago:

Helpful comparison !I was tynirg to get more information on Protocol Buffers, and Wikipedia linked me to Thrift. I found Protocol Buffers pretty well documented, while on the other hand Thrift looks like an alpha project from the documentation point of view It is a pity because Thrift seems to have quite a few interesting features. Considering that  Thrift has been published like one year ago,  I wonder if there is really a community backing it up and any enthusiasm around it ..It is quite an important point, because if you start using any of these libraries to communicate between different servers/services, you will probably have to stick to it for a few years   In addition, it would be interesting to see if these libraries could be used to store hierarchical information in a database and see what would be the performances/limitations compared with storing XML or JSON. They should work better for a basic load/save strategy but what if you just want a subset of  the data, do you still need to read the whole message ?  The same applied if you want to redirect a message depending on one particular field without reading the whole message

view (1 line, 4 lines of output)

Python, pasted 1 hour ago:

Helpful comparison !I was tynirg to get more information on Protocol Buffers, and Wikipedia linked me to Thrift. I found Protocol Buffers pretty well documented, while on the other hand Thrift looks like an alpha project from the documentation point of view It is a pity because Thrift seems to have quite a few interesting features. Considering that  Thrift has been published like one year ago,  I wonder if there is really a community backing it up and any enthusiasm around it ..It is quite an important point, because if you start using any of these libraries to communicate between different servers/services, you will probably have to stick to it for a few years   In addition, it would be interesting to see if these libraries could be used to store hierarchical information in a database and see what would be the performances/limitations compared with storing XML or JSON. They should work better for a basic load/save strategy but what if you just want a subset of  the data, do you still need to read the whole message ?  The same applied if you want to redirect a message depending on one particular field without reading the whole message

view (1 line, 4 lines of output)

Python, pasted 1 hour ago:

A few quick comments:1/ Data size and srliaeization performance are definitely of great importance to Thrift. Huge data sets are definitely one case where this matters, but don't forget about high-throughput low-latency services (at Facebook, like Google, every millisecond counts). Thrift is much quicker than typical XML/RESTful service implementations, even with relatively small data sizes. This is one of the primary use cases. When you're dealing with millions of users and thousands of servers, efficiency really starts to matter.2/ We do have to admit Thrift isn't yet as fully-featured in the documentation department as it could (and probably should) be, but we do have an active and enthusiastic community. Thrift is currently being used and contributed to by Powerset, Rapleaf, iMeem, AmieStreet, the reCaptcha project, as well as a number of independent developers.3/ Both Thrift and Protocol Buffers are great candidates for serializing data into databases   both are more compact and quicker to read/write than XML/JSON. Another common persistent use case is the storage of replayable logfiles.4/ Last point, though Thrift currently only has implementations for binary/JSON, it's designed so that the encoding format is extensible. Thrift could easily support XML or human-readable ASCII   so the trade-off of efficiency vs. readability is left up to the developer.

view (1 line, 4 lines of output)

Python, pasted 1 hour ago:

A few quick comments:1/ Data size and srliaeization performance are definitely of great importance to Thrift. Huge data sets are definitely one case where this matters, but don't forget about high-throughput low-latency services (at Facebook, like Google, every millisecond counts). Thrift is much quicker than typical XML/RESTful service implementations, even with relatively small data sizes. This is one of the primary use cases. When you're dealing with millions of users and thousands of servers, efficiency really starts to matter.2/ We do have to admit Thrift isn't yet as fully-featured in the documentation department as it could (and probably should) be, but we do have an active and enthusiastic community. Thrift is currently being used and contributed to by Powerset, Rapleaf, iMeem, AmieStreet, the reCaptcha project, as well as a number of independent developers.3/ Both Thrift and Protocol Buffers are great candidates for serializing data into databases   both are more compact and quicker to read/write than XML/JSON. Another common persistent use case is the storage of replayable logfiles.4/ Last point, though Thrift currently only has implementations for binary/JSON, it's designed so that the encoding format is extensible. Thrift could easily support XML or human-readable ASCII   so the trade-off of efficiency vs. readability is left up to the developer.

view (1 line, 4 lines of output)

Python, pasted yesterday:

Good Morning Goodnight 
<a href="http://metformin-b2.jigsy.com">metformin fertility side effects in vitro fertilization</a>
[url="http://metformin-b2.jigsy.com"]metformin fertility side effects in vitro fertilization[/url]
http://metformin-b2.jigsy.com metformin fertility side effects in vitro fertilization
 metformin hcl information

...