<html><head></head><body bgcolor="#FFFFFF"><div>Yeah that's been there since the parser was hand rolled. It's since been replaced with a leex and yecc based parser. And I can definitely vouch for its use in production. I've used it in a B2B application with about 30 different partners for about 2 years, probably totaling a couple trillion requests.</div><div><br></div><div>-Anthony</div><div><br>On Feb 26, 2012, at 5:15 AM, Alex Arnon <<a href="mailto:alex.arnon@gmail.com">alex.arnon@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div><div style="text-align: left;direction: ltr; ">This bit in the readme has me worried:</div><div style="text-align: left;direction: ltr; "><br></div><div style="text-align: -webkit-auto;direction: ltr; ">"Support for parsing proto files and creating code from it is volatile and should be considered alpha software at best. Please do not use this in production."<br></div><div><br></div><div>Outdated doc...?</div><br>Sent from my iPhone</div><div><br>On 26 Feb 2012, at 14:02, Jack Moffitt <<a href="mailto:jack@metajack.im">jack@metajack.im</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><blockquote type="cite"><span>I am looking for a production-ready Protocol Buffers implementation for</span><br></blockquote><blockquote type="cite"><span>Erlang. Which is recommended?</span><br></blockquote><span></span><br><span>I'd probably use the one that Riak uses:</span><br><span><a href="http://github.com/basho/erlang_protobuffs">http://github.com/basho/erlang_protobuffs</a></span><br><span></span><br><span>jack.</span><br></div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>erlang-questions mailing list</span><br><span><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a></span><br><span><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a></span><br></div></blockquote></body></html>