Stream: git-wasmtime

Topic: wasmtime / issue #3483 Provide support for wasi-experimen...

Wasmtime GitHub notifications bot (Oct 28 2021 at 14:12):

IhostVlad opened issue #3483:

Feature

Provide support for wasi-experimental-http, for instance, this one https://github.com/deislabs/wasi-experimental-http, over specific CLI flag

Benefit

Currently there is now stereotypical way to perform HTTP requests over wasmtime runtime, but it's mandatory MVP feature, since much work performed via network sockets, for instance, interacting with AWS/Azure/etc cloud SDKs can be performed only via HTTP(S)

Implementation

Support for wasi-experimental-http can be provided as build-in functionality, like for neural nets or cryptography, which are already had been implemented as wasmtime features, and should be available via CLI flag
Maybe it's better to introduce some plugins management subsystem in wasmtime, but now it seems to be redunant

Alternatives

Unfortunately there is now adequate alternatives, other than recompile wasttime from source codes and inject http crate mentioned above

Wasmtime GitHub notifications bot (Jan 15 2022 at 09:33):

wuhuizuo commented on issue #3483:

any updates?

Wasmtime GitHub notifications bot (Jun 02 2022 at 10:23):

IhostVlad commented on issue #3483:

@wuhuizuo @alexcrichton @pchickey @abrown Any updates or planned milestones for this issue? Still waiting for HTTP or TCP support to try wasmtime in project :)

Wasmtime GitHub notifications bot (Jun 02 2022 at 10:23):

IhostVlad edited a comment on issue #3483:

@sunfishcode @alexcrichton @pchickey @abrown Any updates or planned milestones for this issue? Still waiting for HTTP or TCP support to try wasmtime in project :)

Wasmtime GitHub notifications bot (Dec 27 2022 at 15:58):

brendandburns commented on issue #3483:

@IhostVlad

I built a small patch set on top that integrates this into wasmtime:
https://github.com/brendandburns/wasmtime/tree/v4.0.0

And at head:
https://github.com/brendandburns/wasmtime

Please note that this is a personal experiment, so YMMV and all of that.

If the wasmtime maintainers are interested in this as a pull request, I can clean it up and send it over, but I definitely respect their decision about what to include (or not) in wasmtime.

Wasmtime GitHub notifications bot (Dec 27 2022 at 15:59):

brendandburns edited a comment on issue #3483:

@IhostVlad

I built a small patch set on top that integrates this into wasmtime:
https://github.com/brendandburns/wasmtime/tree/v4.0.0

And at head:
https://github.com/brendandburns/wasmtime

Please note that this is a personal experiment, so YMMV and all of that.

If the wasmtime maintainers are interested in this as a pull request, I can clean it up and send it over, but I definitely respect their decision about what to include (or not) in wasmtime.

I'll be putting together some better documentation and examples over the next few days.

Wasmtime GitHub notifications bot (Dec 30 2022 at 23:30):

brendandburns commented on issue #3483:

There's a bunch of examples of how to use this from various languages now:

• C
• TypeScript
• Golang
• Zig

Wasmtime GitHub notifications bot (May 24 2023 at 13:41):

brendandburns commented on issue #3483:

Now that wasmtime 9.0.x has shipped with this enabled, I think that this issue can be closed.

Wasmtime GitHub notifications bot (May 24 2023 at 14:58):

pchickey closed issue #3483:

Feature

Provide support for wasi-experimental-http, for instance, this one https://github.com/deislabs/wasi-experimental-http, over specific CLI flag

Benefit

Currently there is now stereotypical way to perform HTTP requests over wasmtime runtime, but it's mandatory MVP feature, since much work performed via network sockets, for instance, interacting with AWS/Azure/etc cloud SDKs can be performed only via HTTP(S)

Implementation

Support for wasi-experimental-http can be provided as build-in functionality, like for neural nets or cryptography, which are already had been implemented as wasmtime features, and should be available via CLI flag
Maybe it's better to introduce some plugins management subsystem in wasmtime, but now it seems to be redunant

Alternatives

Unfortunately there is now adequate alternatives, other than recompile wasttime from source codes and inject http crate mentioned above

Last updated: Nov 22 2024 at 16:03 UTC