I feel that this suggestion is a bit of a red herring. Sure, you could implement a tiny fraction of the Thrift "library" in C - maybe just the protocol? - but then you'd still be stuck needing the full code generator and a set of related language-specific tools. I'm thinking that even if you coded up the core of the protocol in C, you'd probably have to put a language-specific C-extension wrapper on it in order for it to be usable in the way that all the languages operate.
Bottom line, I don't think there's near enough benefit to putting the "core" in a common C blob. I could be convinced otherwise if someone has some strong ideas. On Sun, Aug 15, 2010 at 5:01 PM, Mayan Moudgill <ma...@bestweb.net> wrote: > > > Todd Lipcon wrote: > . Moreover, Cassandra is a lot easier to accept patches > >> for, as it's a single-language project where most of the code is used by >> most of the people, where Thrift is 15-language project where most people >> use 20% of them. >> > > If I may put in $0.02 - that is the main design decisions which I wonder > about. Why not write the core in C and export the functions via wrappers to > each of the 15 languages? Among other things, this would enable any > improvements in the underlying communication infrastructure to be available > to everyone. >
