WASI support

[Zykino]

Hello,

I’m creating WASM plugins for zellij and I would love to have some ways to access dbus to send messages. At least for now I only have ideas to access dbus as a client (sending desktop notification when certains event happens, integrate a mpris-player-ctl so I can control the music from keybindings anywhere from my terminal, …).

I would love to find a library that could help. For now I’m relying on calling busctl and interpreting its json… which is not that good (and less portable than using an actual lib).

At first I though your lib was not usable since even your blocking interface require an async runtime, but at least tokio have some limited support for WASM: https://docs.rs/tokio/latest/tokio/#wasm-support.

Do you think this may happens someday? Or tokio’s support lack some crucial features?
On zellij’s side, I cannot guarantee full hard drive access, but I can point the "cwd" to whichever directory is needed, so it would be best if I could enter the unix socket’s I want to use instead of letting the lib decide for itself.

[zeenix]

Do you think this may happens someday? Or tokio’s support lack some crucial features?

TBH I have absolutely no idea. While WASM is close to my heart, I never got around to play with it.

If you're interested in this, I'd say you should try things out and see if there is anything missing from tokio. I don't think "async" is really the problem here (but I might be completely wrong).

On zellij’s side, I cannot guarantee full hard drive access, but I can point the "cwd" to whichever directory is needed, so it would be best if I could enter the unix socket’s I want to use instead of letting the lib decide for itself.

That's not at all a problem. zbus has API to specify your own D-Bus address and you can also modify it using environment variables.

[Zykino]

(Renaming to WASI, as WASM is in the browser, and WASI is the VM.)

I could try a bit, but not knowing zbus it may be difficult for me. I can code in Rust, but I don’t know well the cargo workspace nor the cargo features.

Should I set this in zbus/Cargo.toml to add a new feature?

tokio-wasi = { workspace = true, optional = true, features = [
    "rt",
    "time",
    "sync",
    "tracing",
] }

For now my way of testing is to have another repo use zbus as a local dependency… which is not the most developer friendly.

Do you know how I could test with the "wasm32-wasip1" target and my new tokio-wasi feature?