jsonrpc VS rlua

paritytech has a Rust JSON-RPC framework.

JSON-RPC (https://github.com/paritytech/jsonrpc) might be a solution, so I can create a TCP connection and it can then stream JSON request/response.

This is an async implementation of JSON-RPC, from Parity, who also created the popular jsonrpc crate.

Hi, I am looking for a fairly stable JSON-RPC implementation over stdin/stdout. I want to implement a plugin architecture similar to Xi-Editor or Nushell. I am aware of Parity JSON-RPC and am wondering how it compares to tonic (gRPC implementation). A very brief search on GitHub revealed that jsonrpc_stdio_server appears to be not that heavily employed by others; therefore, I am leaning towards tonic. However, since I am a Rust beginner, I am a little bit lost about where to start.

There's the rlua package for running lua in your rust app: https://github.com/amethyst/rlua

Some sys crates do embed the source files, like rlua for example.

[1] - https://github.com/amethyst/rlua/blob/master/examples/guided_tour.rs

Yes though, given that a CCleaner/BleachBit-style situation is going to be I/O-bound, I'd probably go with rlua, PyO3, or rust-cpython for plugins.

I wrote up some rust low-level bindings for guile [1]. The problem is that Guile liberally uses setjmp/longjmp, which breaks rust destructors. It might be possible to fix this by wrapping every call the way rlua does [2], but I'm not familiar enough with Guile to know.

1: https://github.com/ysimonson/guile-sys

2: https://github.com/amethyst/rlua/issues/21

And.. another binding finally called rlua https://github.com/amethyst/rlua

hlua or rlua are what you want for Lua, rust-cpython or PyO3 for Python, rutie for Ruby, and possibly deno_core for JavaScript.

Janet is what introduced me to Fennel. Conjure [1] sold me on Fennel over Janet. The Neovim community is rallying around Lua.

(And in fact, what sold me on Rust was its truly excellent Lua FFI support [2].)

[1]: https://github.com/Olical/conjure

[2]: https://github.com/amethyst/rlua