Roadmap

[frol]

Hey, I am quite interested in Rust implementation of WAMP as I want to use it in my projects. I would love to use both RPC and PubSub, and also async/await-based API would be nice to have. I can offer my help in implementing that.

[fin-ger]

Sorry for the late answer.

The scope of this project is to write a distributed WAMP-Server implementation which is purpose built for a Kubernetes deployment. However, we (@jwuensche, @martin31821) thought about a project called asphalt-rs which would include the parsing and connection management (and maybe more parts of autobahnkreuz-rs). asphalt-rs could then be a basis for a separate client-side implementation and the autobahnkreuz-rs routing application. Are you interested in writing up your thoughts on the client-side API? We could then make sure asphalt-rs fits for your needs.

[frol]

I am not sure about the exact API, but I have a set of general requirements for my projects communication (these are not related to autobahnkreuz-rs):

• "Native" support for Web-platform (e.g. gRPC does not support Web-platform natively as it requires a low-level control over HTTP2 communication, and thus it only works via gRPC-Web proxy). Thus, WAMP-proto is a great match for my use-case.
• I would like to be able to embed WAMP router for a single-executable user application implemented in Rust (sort of Docker daemon + Docker CLI design with an option to implement WebUI as well).
• Client and router implementations should have async/await API to be ergonomic to use/contribute to.

I have had experience with Python, Node.js and client-side JS clients, and I find their API design good enough (they still require some hacking since they provide barebone interfaces for Connection, though Python implementation, at least, provide helper decorators to register handlers).