logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-02 14:13:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixing typos and namings on review findings

Browse Source
This commit is contained in:
NagyZoltanPeter 2024-09-17 11:18:51 +02:00
parent 90efdfa6af
commit 6a0041544b
No known key found for this signature in database
GPG Key ID: 16EADB9673B65368
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
standards/core/peer-exchange.md
View File

@ -94,12 +94,12 @@ Responders, MUST include a `status` in the response in any case and possible des
| Result | Code | Note |
|--------|------|------|
| SUCCESS | 200 | Successfull request-respond. In response the answer must contain `PeerExchangeResponse` |
| BAD_REQUEST | 400 | Wrong request payload. It must only contain `reques` field. |
| BAD_RESPOND | 401 | Wrong respond payload. If success it must contain `respond` and `response_status` fields. If failure, only `response_status` is set. |
| SUCCESS | 200 | Successfull request-respond. |
| BAD_REQUEST | 400 | Wrong request payload. It must only contain `request` field. |
| BAD_RESPONSE | 401 | Wrong response payload. If success it must contain `response` and `status` fields. If failure, only `status` is set. |
| TOO_MANY_REQUESTS | 429 | DOS protection prevented this request as the current request exceeds the configured request rate. |
| SERVICE_UNAVAILABLE | 503 | Request cannot be served, either issue on Responder side or having no suitable peer to issue request. |
| DIAL_FAILRE | 599 | Requester side problem calling PeerExchange peer. |
| DIAL_FAILURE | 599 | Requester side problem calling PeerExchange peer. |
## Implementation Suggestions