Viktor Klang (√)

This issue of ours seem to have been recently closed: https://github.com/oracle/graal/issues/2736 https://github.com/oracle/graal/issues/2369

Graalvm 20.3 has been released: https://www.graalvm.org/release-notes/20_3/

@jroper Is this issue still relevant?

After thinking about this topic for a bit, I propose that we formalize the specification *within* the proto files as documentation, that way the protocol and its specification lives side-by-side...

Looks like it is an option to use this plugin to then export the specification from the proto files to publishable documents: https://github.com/pseudomuto/protoc-gen-doc

Hi Sam, seems related to this: https://github.com/cloudstateio/cloudstate/issues/176 moving the conversation there.

Reopening this since there could be a different option: https://github.com/lomigmegard/akka-http-cors/blob/master/akka-http-cors-example/src/main/scala/ch/megard/akka/http/cors/scaladsl/CorsServer.scala

Another option is to have the gateway deal with the CORS support—by configuring the CORS policy when defining the routes.

After talking to @jroper about this, I think going with gateway configuration seems to be the easiest forward path. And it can be argued that it is a gateway concern...

@sleipnir Having thought about it for a little while, how about starting with CommandHandler, and then we can rename it when/if we find that something else is more appropriate?