Amazing how people can live without it and never complain. The first express routes I define in new (home) projects are /bus/{call,notify}, which do the same under the similar js api (no type checking, no proxying). Maybe I should ditch it in favor of this at some point. My api looks something like this, minus sugar and `this` bindings:

  bus.method(“auth.login, (params, client) => {…})

  bus.on(“auth.logged_in”, (params, client) => {…})

  bus.call(“auth.login”, …params)

  bus.notify(“auth.logged_in”, …params)

You can also call/notify in every direction (via `client` handle to one, via `bus` handle to all clients). Works through web sockets.

If you don’t mind, I’d suggest considering notification mode, which doesn’t require awaits, and uses navigator.sendBeacon() under the hood. For events that do not assume any answer by design, like “user moved to section X”.

Also, does it by chance have call/result logging?