-
-
Notifications
You must be signed in to change notification settings - Fork 106
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:
{
"metadata":{
"q":"someQualifier"
},
"data":{
"key": "value"
}
}
where:
Param | Required | Description |
---|---|---|
metadata | Required | colects object "q" |
q | Required | qulifier to identify an entrypooint |
data | Required | request data |
Response example:
{
"data":{
"key": "value"
},
"metadata":{
"q": "/qualifier/req-resp"
}
}
and then followed optional (for sandbox client) relevant stream complete signal message:
"Completed!"
where:
Param | Required | Description |
---|---|---|
data | Required | response data, except for completion response |
metadata | Required | colects object "q" |
q | Required | qulifier to identify an entrypooint |