Tushar Mathur

The current API allows sending a message without waiting for one from the client (collect on handshake event). ChannelEvents are a bit complex, but can give a lot of performance...

One change that we should consider while doing this change is to make sure that the client and the server use the same event loop and the same transport.

@carlos-verdes I have updated the readme with the installation instructions. https://github.com/zio/zio-http/blob/main/README.md#stable

@frekw This would be a great addition to the ZIO Http ecosystem. I think it would better to maintain it as separate project, in the same repo.

Let's keep the issue open, until it's resolved @vigoo. Pinning it so that everyone is aware.

WIP, we are very close 🙌

@gauntface I have a configuration based setup where the configs are loaded in a global variable `APP_CONFIG` **sw.js** ``` js import toolbox from 'sw-toolbox' const swConfig = APP_CONFIG.sw if (swConfig.preCache)...

> Generally if CORs isn't enabled and you are trying to cache it, you are in risky waters since you'll never know if something is cached correctly or not How...

@gauntface Status code won't be available for same origin requests either (IFAIK). So why should I be especially concerned about CORs requests? Sorry, but I am a complete noob when...

I can pick this up. The below code would work. ``` js function transform (i, fun) { const out = {} const keys = Object.keys(i) keys.map((key, index) => out[ key...