You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, you can control the simulator by executing command on its prompt.
It's good for interactive use, but not that much for playing "demo scenario" or "test script".
Ideally, the simulatior should be totally controllable through a REST API (exposing all the command that exists in the shell, plus some other such as "add node", "remove node", …).
The goal of this issue is to design and implement a REST API for the simulator (TBC: it will probably rely on Swagger).
restbed seems to have a licensing policy that wont be compatible with our goal
So, we will probably have to build something ourselves on top of libmicrohttpd (will create a dedicated issue for that).
As for Swagger, seems like we won't be able to benefit from the code generation from the YAML specs, because the code generator for server relies on restbed for C++.
That being said, I still think it's worth to have a Swagger spec (it will allows people to auto-generates REST clients for our API in others languages), we will have to write it by hand though (maybe with the help of https://editor.swagger.io/).
Currently, you can control the simulator by executing command on its prompt.
It's good for interactive use, but not that much for playing "demo scenario" or "test script".
Ideally, the simulatior should be totally controllable through a REST API (exposing all the command that exists in the shell, plus some other such as "add node", "remove node", …).
The goal of this issue is to design and implement a REST API for the simulator (TBC: it will probably rely on Swagger).
This issue is a prerequisite for #36.
The text was updated successfully, but these errors were encountered: