APIs are central for XBR, as that is what XBR services implement. A XBR Consumer naturally will need information on the API to consume, and depending on kind of API, the expectation regarding the typing strictness of the API could range to "fully statically typed".
So what we need in XBR is an interface definition language to specify more or less typed WAMP interfaces with additional XBR related information.
The steps:
[ ] sketch out examples
[ ] add Xtext project for a Netty/ABJ/Xtext-server backend for connecting a Web editor running in a browser via WAMP to the Xtext editor backend
oberstet
commented
5 years ago
APIs are central for XBR, as that is what XBR services implement. A XBR Consumer naturally will need information on the API to consume, and depending on kind of API, the expectation regarding the typing strictness of the API could range to "fully statically typed".
So what we need in XBR is an interface definition language to specify more or less typed WAMP interfaces with additional XBR related information.
The steps: