There's also something to be said for compile time checks in Java and C++.
> Mainly, the ability to deserialize data in consumers without knowing the > schema at development time So, this is using thrift for storing structured data and later deserializing it? On 11/11/08 10:41 AM, "Chad Walters" <[EMAIL PROTECTED]> wrote: I think there is a place for both static generation and dynamic generation -- I'd personally love to see Thrift embrace both. Getting high performance in C++ is one of the key drivers of static generation, I think. I realize that not everyone is interested in C++, but Thrift's heritage includes a healthy dose of C++. Chad On 11/11/08 9:38 AM, "Martin Traverso" <[EMAIL PROTECTED]> wrote: > Interesting. What is your use case? Mainly, the ability to deserialize data in consumers without knowing the schema at development time. But there's a couple of other things that prompted me to try this approach: * Serializable objects are not tied to Thrift's hierarchy. They don't need to extend from TBase. The only requirement is for them to have appropriate setters and getters. Or if you don't even have javabeans, you can get the data placed in a Map<String, Object> * I think static code generation is not the right approach in general. It makes development more cumbersome. I know the analogy is not perfect, but compare to old day RMI where you had to create the stub and skeleton files from your class file and today's approach, where it uses dynamic proxies instead. Martin
