-
-
Notifications
You must be signed in to change notification settings - Fork 107
Rsocket API
Pavlo Petrina edited this page Jan 15, 2019
·
13 revisions
Basically, all the requests handling proceed under the WS protocol so it's impossible to observe the stream behaviour upon the RS protocol is used so the following actions were done:
- Foreign library implementation > Rsocket.io / GIT
- Improvements for scalecube sandbox client > JS
Request example:
{
"data":{},
"metadata":{
"q":"someQualifier"
}
}
where:
Param | Required | Description |
---|---|---|
metadata | Required | colects object "q" |
q | Required | qulifier to identify an entrypooint |
d | Required | request data |
Response example:
{
"q": "/qualifier/req-resp",
"sid": 1,
"d": {
"key": "value"
}
}
and then followed the relevant stream complete signal:
{
"sid": 1,
"sig": 1
}
where:
Param | Required | Description |
---|---|---|
q | Required | qualifier to identify an entry point |
sid | Required | stream identifier |
sig | Optional | completion signal, no responses after given such type of response for the given stream ID |
d | Optional | response data, except for completion response |