Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1084
This is significant enough that I think some level of design write-up is
warranted. At some point we'll want to update the top level doc's and
diagrams, but I'm OK with that being a follow on
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1084
Yeah, I tend to agree @ottobackwards . There is a high level diagram in
the use-case under the "High Level Solution" section; do you think that should
be extracted out into its own document along
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1084
Yes. The use case is useful, but this is more dev. focused, if that makes
sense.
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1084
@ottobackwards Yeah, that is a really good point. I'll write up something.
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1084
@ottobackwards Ok, let me know what you think about
[this](https://github.com/cestella/incubator-metron/blob/enveloped_message_supplier/metron-platform/metron-parsers/ParserChaining.md).
Is it too
