Sort 11 Discussions, By:
Please Login in order to post a comment
The answer is incorrect, as you could have server initiated RPC as well (in case of remote callbacks).
This was exactly what I was thinking, @HackerRank admins, shouldn't the answer be both server and client.
I agree too !!!
Actually client/server are just roles of applications. One application could be a client and also can be a server. The role of the application is determined by what the application is doing instead of how you define the application.
So, put the term "rpc" here does not make any sense. Jut put a dummy question to determine what is client and what is server.
Couldn't agree more, seems like the wrong answer here
Message passing. RPC is a request–response protocol. An RPC is initiated by the client, which sends a request message to a known remote server to execute a specified procedure with supplied parameters
Do you have any suggested tutuorials or readings to finish before attending questions in "Distributed Systems"?
This seems like a semantics problem.
Who initiates the RPC is dubbed client and who executes it is the server. There can be interchangeable roles.
RPC is a request–response protocol. An RPC is initiated by the client, which sends a request message to a known remote server to execute a specified procedure with supplied parameters.
i just started and this is a good site
Answer should be 'both'.
This is a form of client–server interaction (caller is client, executer is server)
@HackerRank Shouldn't the answer be both? As rpc calls can be intiated by server as well as client
Please change the answer!
Any application can initiate a RPC. Please fix the right answer choice.
Answer is correct. By definition of "client" and "server".
This is wrong. Both client and server can initiate RPCs.