REST

[KrishnaPG]

Somewhat out of context - but wondering if anyone has some suggestions:

• what is the right way to use / expose the underlying RPC endpoints as REST endpoints also?

With RPC and Pub/Sub under the same hood, the only thing left is REST capability - that way we can cover all the spectrum (of clients).

RPC is good, but demanding websocket for it to work is kind of inconvenience (as opposed to simple REST, from say CLI).

Is there anyway, this Bonefish can be extended to support REST for the underlying RPC (for example,auto-generate the REST wrappers for the RPC endpoints , something on the lines of swagger??)

[davidchappelle]

If you look at crossbar.io you will find that it has the ability to expose HTTP through an embedded web server. I think that the approach to supporting REST would be to follow a similar approach in Bonefish. An embedded web-service could then be hosted that translates REST to WAMP RPC calls. Since WAMP procedures are named using URIs, there could be a direct translation from REST to a corresponding WAMP URI.

[davidchappelle]

Looks like crossbar.io now supports REST bridging. I would recommend taking a close look at this as a design reference.