LEdoian
/
recodex-wiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update

Browse Source
master
Petr Stefan 8 years ago
parent 768ed4050c
commit 8f9eff508e
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File

12
Rewritten-docs.md
Unescape Escape View File

@ -3780,7 +3780,7 @@ is reliable and can outlive short term issues with connection without problems.
Also, increasing delay of ping messages does not flood the network when there Also, increasing delay of ping messages does not flood the network when there
are problems. We experienced no issues since we are using this protocol. are problems. We experienced no issues since we are using this protocol.
### Worker - File Server Communication ### Worker - Fileserver Communication
Worker is communicating with file server only from _execution thread_. Supported Worker is communicating with file server only from _execution thread_. Supported
protocol is HTTP optionally with SSL encryption (**recommended**). If supported protocol is HTTP optionally with SSL encryption (**recommended**). If supported
@ -3856,7 +3856,7 @@ discarded.
"Broker - Worker Communication" chapter above. "Broker - Worker Communication" chapter above.
### Broker - Web API Communication ### Broker - REST API Communication
Broker communicates with main REST API through ZeroMQ connection over TCP. Broker communicates with main REST API through ZeroMQ connection over TCP.
Socket type on broker side is ROUTER, on frontend part it is DEALER. Broker acts Socket type on broker side is ROUTER, on frontend part it is DEALER. Broker acts
@ -3911,10 +3911,10 @@ they are stored in the persistent database for further consideration.
For the details of this interface please refer to the attached API documentation For the details of this interface please refer to the attached API documentation
and the `broker-reports/` endpoint group. and the `broker-reports/` endpoint group.
### File Server - Web API Communication ### Fileserver - REST API Communication
File server has a REST API for interaction with other parts of ReCodEx. File server has a REST API for interaction with other parts of ReCodEx.
Description of communication with workers is in "Worker - File Server Description of communication with workers is in "Worker - Fileserver
Communication" chapter above. On top of that, there are other commands for Communication" chapter above. On top of that, there are other commands for
interaction with the API: interaction with the API:
@ -3935,7 +3935,7 @@ interaction with the API:
There are no plans yet to support deleting files from this API. This may change There are no plans yet to support deleting files from this API. This may change
in time. in time.
Web API calls these fileserver endpoints with standard HTTP requests. There are REST API calls these fileserver endpoints with standard HTTP requests. There are
no special commands involved. There is no communication in opposite direction. no special commands involved. There is no communication in opposite direction.
### Monitor - Web App Communication ### Monitor - Web App Communication
@ -3971,7 +3971,7 @@ Message format:
- **task_state** -- state of task with id **task_id**. Present only if - **task_state** -- state of task with id **task_id**. Present only if
**command** is "TASK". Value is one of "COMPLETED", "FAILED" and "SKIPPED". **command** is "TASK". Value is one of "COMPLETED", "FAILED" and "SKIPPED".
### Web App - Web API Communication ### Web App - REST API Communication
The provided web application runs as a JavaScript process inside the browser of The provided web application runs as a JavaScript process inside the browser of
the user. It communicates with the REST API on the server through the standard the user. It communicates with the REST API on the server through the standard

Write Preview
Loading…
Cancel
Save