wagi

WAGI and WCGI are the WASM based spiritual successors. https://github.com/deislabs/wagi https://wasmer.io/posts/announcing-wcgi

Compile a CGI program in any language to WASI, then use https://github.com/deislabs/wagi to run it.

Yeah of course! They've got STDIN/STDOUT/STDERR and I've built a Virtual Filesystem. But if you're using WASI binaries locally they don't have that restriction. You might be interested in WAGI: https://github.com/deislabs/wagi And to catch up on WASI: https://xeiaso.net/talks/unix-philosophy-logical-extreme-was...

I've always loved the simplicity and flexibility of CGI. To check my understanding: since CGI just takes a raw request over stdin and returns a response over stdout, would a WCGI wasm module be compatible with WAGI[1] and vice-versa? [1] https://github.com/deislabs/wagi

What do you think of WAGI [1], which is basically CGI for WASM modules. [1]: https://github.com/deislabs/wagi/blob/main/docs/writing_modu...

Yup, but they have a lot of different awesome projects on the fire, it can be hard to know which one to use: - https://github.com/deislabs/runwasi - https://github.com/deislabs/hippo - https://github.com/deislabs/wagi - https://github.com/deislabs/krustlet The description at the end of the article sounds like CGI, on WASM, which is what WAGI is.

Towards the end of the article it sounds like the author was looking for this: https://github.com/deislabs/wagi

> - JS is notably missing from the list of languages supported on the front page. But I see mentions of a Spidermonkey.wasm in the blog post. Is running JS on top of wasmtime in production a realistic prospect today? If so, where can I read more? (mainly interested in this for the instantiation time benefits, though maybe all/most of that will be negated by the embedded JS engine?) Shopify and others use QuickJS as their JS engine of choice. See https://github.com/Shopify/javy as a starting point. The real benefit is allowing authors of plugins to write JS and not AssemblyScript, not any performance or instantiation time benefits. > - How should I go about building a typical web service on top of wasmtime? Can wasmtime itself handle network requests/connections or would I need to build the web server in some other host language and pass r

I'm experimenting with WASM & Rust but with a different framework named wagi [1], there's a great video by Rainer Stropek & Stefan Baumgartner that gives a little introduction to it [0] [0]: https://www.youtube.com/watch?v=9NDwHBjLlhQ [1]: https://github.com/deislabs/wagi

Hi, one of the maintainers here. It does support outbound HTTP, the runtime we are currently using enables that -- see https://github.com/deislabs/wagi/blob/main/docs/writing_modu... Good point on the docs, I will open an issue and add some information about it, thanks!

RFC2616 says this: "It MUST be possible to combine the multiple header fields into one "field-name: field-value" pair, without changing the semantics of the message, by appending each subsequent field-value to the first, each separated by a comma." So, if the implementation folds the multiple headers into one with the various values as a comma separated list, it should all be compliant. I don't know rust well enough to tell if this one is compliant...it reads like it is not (looks like last header wins): https://github.com/deislabs/wagi/blob/main/src/http_util.rs#... Edit: It seems RFC7230 keeps most of that language, but makes one exception for Set-Cookie, but that's outbound in this context so it doesn't apply.