Jonathan Halliday

A lot depends on what you want to support as the stable public API for the simdjson library. The cleanest language integration may be to make the tape formats part...

The current iteration of the prototype uses two different interfaces. The static version is simply `SchemaData getSchema();` whilst the dynamic version is ``` SchemaData getSchema(ILoggingEvent evt); boolean checkConformance(ILoggingEvent evt, SchemaData...

> since each event could have their own dynamic content. i.e. Not all events would be guaranteed to follow the schema generated by the first logged event. yes, that's kind...

The polymorphism permitted by the application requirements is usually a very narrow subset of that permitted by the logging API. For many use cases it's further constrained by utilizing a...

ok, preliminary version for the the static-only case is at https://github.com/jhalliday/logstash-logback-encoder/tree/schemas It's easy to see that changes for flipping from schema validation to schema generation would be confined to the...

With the metrics effort hitting release candidate stage (yay!) we're hopefully approaching a period when reviewers have a bit more time available. However, that only matters if there is something...

Using synchronized for CPU bound code may come under the 'if it ain't broke, don't fix it' rule, except possibly in so far as there is something to be said...

Some notes extending and modifying my previous position: Metadata relating to prepare and commit ordering could also be used to inform enlistment decisions. These issues are somewhat related, as e.g....

Time to pick this up again after my PTO. If there are no more questions, I guess the next step is to redraft the PR with all the additional material...

> I'm not sure that mirroring the protos exactly is a great way to build out our SDK classes. We have the opportunity to build something better than raw protos...