On Thu, Aug 26, 2010 at 6:33 PM, Greg Stein <[email protected]> wrote:
> ASN.1, huh? I clicked that link. Couldn't find an overview link. > "Papers" and "presentations" and "consortium members" and all that. > > Wikipedia has a more reasonable introduction. All those consortia > members should learn from that, rather than worrying about their > "international standard". :-P > > That said, ASN.1 is about both description and on-wire formats. If > Thrift used ASN as the descriptive language, then people might think > it also uses the same wire format. And ASN.1 might not have things > like field tag numbers, needed by Thrift. > > I don't think we're talking about a new IDL here. Just the technology > to convert those into compilable runtimes. > > Yes, any incompatible change in IDL would be hugely awful. If we plan to experiment with switching the compiler to a different language, the acceptance test should be that it can take any thrift file and generate hashwise identical code for all of the currently supported languages. -Todd > Cheers, > -g > > On Thu, Aug 26, 2010 at 21:22, Roger Meier <[email protected]> > wrote: > > talking about interface descriptions and languages to build to compiler. > > > > What about ASN.1 (http://www.asn1.org/) as a discription language or pre > > format? > > > > Does somebody have a ASN.1 to Thrift compiler ? > > > > Of course there might be some gaps, but what about that? > > > > > > Am 26.08.2010 22:54, schrieb Bjorn Borud: > >> > >> on the project I currently work on we have a (ANTLR-based) parser for > >> the Thrift IDL language in order to generate code for a proprietary > >> serialization library. > >> > >> it struck me that perhaps we could use this parser the implement the > >> Thrift compiler in Java instead. this would mean that the thrift > >> compiler itself could be built as a platform independent artifact -- > >> which should make it a lot more elegant to write Maven plugins for > >> Thrift. it would also eliminate the need (for us) to maintain Thrift > >> compiler binaries for all platforms and versions of the compiler. > >> > >> currently the parser lacks some minor features, but this could easily be > >> rectified. the real job is to add the code generation for various > >> languages. > >> > >> if anyone is interested in this, I am going to talk to some people > >> tomorrow to get formal approval for open sourcing it. > >> > >> any thoughts? > >> > >> -Bjørn > >> > >> > >> > >> > > > > > -- Todd Lipcon Software Engineer, Cloudera
