Age | Commit message (Collapse) | Author | Files | Lines |
|
They were stored in the mapis sections instead of the events
one.
Clean and handle raw events as well. Before that it could
only process events coming from monitoring api. Now it could
receive the event directly.
Make sure that the event handle is valid before sends the
request response. This prevent to subcribe or push an event
while the event handle hasn't been correctly created. This
could happens if the testVerb hasn't not been called from a
session. In that case, the response will just be that tests
has been launched.
Format.
Change-Id: I0aa522939162684f91dd426cc14919bb0ec3f69e
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Add each Mock API event's action to the Mock API
controller section.
Change-Id: I072b7f2c610cf28760880e02629cafd38dafeb6b
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Beginning work to handle events from a Mapi.
Also rename old fapis file to mapis and some format
Change-Id: I30bedcbe13cac9568e21cd3a0947516e74dde271
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
An m(ock)api is a plugin with its action as verb. About
now the event listener is the same then the main api
Change-Id: Iadbbb60cfbe9d5ef85801c346e6565ccde92b0c4
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|