On 2017-10-20 06:36, Matt Sicker wrote:
On 19 October 2017 at 14:05, Mikael Ståldal <mi...@apache.org> wrote:
And don't forget a corresponding LogEventParser.
Right. The basic idea here would be to provide both a reference encoder and
decoder. If an existing binary format such as BSON, Avro, or Thrift were
appropriate, then there wouldn't be much need here other than publishing a
schema, but all 3 of those projects create non-trivial garbage during
encoding and don't really have a use case in minimal memory usage or high
performance encoding like we strive for in log4j.
What about Google's Protocol buffers?
