-
Couldn't load subscription status.
- Fork 1
Communication between Name and Storage servers
First,
- in the config of Storage server we define IP address of Name server
- in the config on Name Server we define Network, where we expect Storage Server connections from
After Storage server was launched, it sends message that it was launched to the Name server

After this action, Name server will add the Storage Server into the list of Storage Servers. Now there are several possibilities for new communications between Name Server and Storage server.
Possible reasons of communication:
- Give token for giving file to client
- Give token for getting file from client
- Give token for getting file from server
- Evaluation of custom command
- Ping Storage Server
For all these scenarios, there is a single schema of communication:

Request format:
- Give file to user or to storage server

- Get the file from user

- Get the file from server

- Eval of the given command

- Ping

Response format:

This might be in only one case - Reporting. Report format

Response for report the same as Storage Server's response: Single byte with status code

This might be in only one case - when one storage server needs to download a file from another.

And, then

Communication with the Name Server was described above, and communication between Storage Servers as the same as between Storage Server and Client
Lost? Return to the home page