Replies: 3 comments
-
hey @gedw99 - Waxosuit's author here. 👋 Just trying to clarify what exactly you're looking to do. WASI is a low-level standard that converts syscalls / libc invocations into Wasm imports, so that stuff is far below the level of protocol buffers. I have some stuff simmering that will hopefully extract some of the "RPC over Wasm" code that Waxosuit uses into something that's a little more generic. Is that what you're looking to do? |
Beta Was this translation helpful? Give feedback.
-
There are a bunch of protobuf and RPC libraries that should be portable to WASI. @gedw99 could you clarify what the exact problem is that wasmer needs to address or close this issue? |
Beta Was this translation helpful? Give feedback.
-
Hey I started to use suborbital. basically I am wanting to host wasm from users ( they they compiled and uploaded into the systemi ) in my servers and in my golang clients . A good analogy is caddy . It is a proxy to run and expose other binaries . Well I want to do the same thing for wasm . Does the analogy work for you ? |
Beta Was this translation helpful? Give feedback.
-
See https://waxosuit.io/
Basically I want a standard protobuf interface for anything I write to run inside a WASI / Wasm runtime.
Waxosuit has done a great job on it. Its following the Mozilla specs too
Without a standard reusable cross language approach it's terrible to write and support WASI.
Protobuf is practically a standard.
Beta Was this translation helpful? Give feedback.
All reactions