For example, a DataNode. Or you can even use Java serialization. RPC and Serialization with Hadoop, Thrift, and Pro. Hadoop beats terabyte sort record.

I use Apache Thrift protocol for tablet-server and interlanguage integration, and all is OK few years. Integration is between languages (C#/C++/PC Java/Dalvik Java) and thrift is probably one of simplest and safest. So I want pack-repack sophisticated data structures (and changed over years) with Thrift library. Lets say in thrift terms kind of OfflineTransport or OfflineProtocol. Scenario: I want to make backup solution, for example during internet provider failure process data in offline mode: serialise, store, try to process in few ways. For example sent serialised data by normal email via poor backup connection etc. Question is: where in Thrift philosophy is best extension point for me?

I understand, only part of online protocol is possible to backup offline, ie real time return of value is not possible, that is OK. Vagrant Web Social Button Download Free on this page.