John Fallows

@cagecurrent we have first class support for gRPC in the `grpc` binding, so that seems like a natural place to potentially add support for the standard [`grpc.health.v1`](https://github.com/grpc/grpc-proto/blob/master/grpc/health/v1/health.proto) service. For example:...

> Hi, @jfallows, Is there anything left that's preventing this from being merged? @Yoni-Weisberg The build is passing but the `http.kafka.avro.json` example is no longer passing the automated test. See...

Note: when running `zilla` engine directly from the test, we should also use `JUnit5` and a per-thread engine directory in `target/zilla-itests` to support parallel test execution.

@ccsrvs @rupurt What is the source for your `OAUTHBEARER` tokens? They would have an expiration and need to be refreshed periodically?

Hey guys, thanks for the feedback. SSE does have a standard content type for http responses, defining the SSE protocol framing, but the message payload defined by the application is...

> > as SSE has its own logical channel of application defined messages > > 🤔 This wasn't obvious to me at first glance. Can't we map AsyncAPI channels to...

> Then I think http://example.com should be a server definition and `/server/sent/events` should be the address of the channel. So better to keep it out of the sse binding. What...

> Yeah, exactly. That would simplify things IMHO. The server protocol could be `http` or `http+sse`. Either way should be fine. @fmvilas I've gone with `http` for now, since there...

Compare minimum Getting Started requirements for Docker, git, etc higher than those supported by WSL ? Double check zilla-examples for requirements too.

[zilla-dump.zip](https://github.com/aklivity/zilla/files/11442831/zilla-dump.zip)