Hi Kenton,
Your right, the reason that one benchmark has those results is because
the implementation does lazy decoding. While lazy decoding is nice, I
think that implementation has a couple of other features which are
equally as nice. See more details about it them here:
http://hiramchirino.c
ing to deal with delayed error-checking.
>
> In your blog post you also mention that encoding the same message object
> multiple times without modifying it in between, or parsing a message and
> then serializing it without modification, is "free"... but how often does
> thi
e case where the
> application code ends up accessing all the fields. If you really think
> there's no significant overhead, prove it. :)
>
> I'd also suggest that you not publish benchmarks implying that your
> implementation is an order of magnitude faster at parsing
oc using
> Runtime.exec()? What's the benefit of having the code generator running
> inside the Maven process? Honest question -- I don't know very much about
> Maven.
>
> On Fri, Sep 18, 2009 at 7:36 PM, hi...@hiramchirino.com
> wrote:
>
>
>
> > Firstly, I want
