I've put together some mock ups of a few different codec strategies both to
compare from an API/usability perspective and to get a rough idea of some
of the performance implications of the different choices. Please see the
attached code for the full details. I'll summarize the different
On Tue, 2014-05-06 at 22:36 -0400, Rafael Schloming wrote:
> I've put together some mock ups of a few different codec strategies
> both to compare from an API/usability perspective and to get a rough
> idea of some of the performance implications of the different choices.
> Please
On Thu, May 8, 2014 at 9:42 AM, Alan Conway wrote:
> I vote for DispatchingDecode: it's the simplest, the fastest and is
> based on a well established parsing pattern with a good track record for
> performance (SAX). Its not so hard to ignore data in a handler.
>
> Writing a handler state machine
Schloming wrote:
> I've put together some mock ups of a few different codec strategies both to
> compare from an API/usability perspective and to get a rough idea of some of
> the performance implications of the different choices. Please see the
> attached code for the full detail
I've put together some mock ups of a few different codec strategies both to
compare from an API/usability perspective and to get a rough idea of some
of the performance implications of the different choices. Please see the
attached code for the full details. I'll summarize the different
