A Lightweight and High Performance Remote Procedure Call Framework for Cross Platform Communication

Bagci, Hakan; Kara, Ahmet

doi:10.5220/0005931201170124

Cited by 4 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This module can strip out the headers, parse the data (if needed), and call any other functions or modules as needed. [6] [7] XML-RPC XML-RPC is one of the simplest web service approaches that was designed in 1998 as an RPC messaging protocol for serializing procedure requests and responses into human-readable XML. The XML format uses HTTP protocol to send data from a client computer to a server computer using traditional web ports for RPC.…”

Section: Third Generation Rpcs and Web Servicesmentioning

confidence: 99%

Analysing RPC and Testing the Performance of Solutions

Király

Szekely

2018

IJCAI

View full text Add to dashboard Cite

In distributed computing, network sockets provide mechanism for a process to establish a remote connection to another process and send messages back and forth. This interface makes possible a proper mechanism that allows a program running as a process on computer A to call a procedure or a function on remote computer B and pass parameters to it. In the case of synchronous Remote Procedure Call (RPC), processes on computer A need to wait for the finishing of execution of procedures on computer B. When the called procedure finishes, produces its result and passes it to the process on computer A that can continue execution. The question is what happens between the time of the remote procedure call and arrival of the returned values and how much the caller must wait for result. Prompted by the release of Protocol Buffers and gRPC by Google, this paper answers that question, describing the structure of third generation RPCs and analysing them putting the focus on performance and the way of marshalling parameters. To facilitate the choice between them this paper represents the results of performance tests carried out by the authors. Povzetek: Podana je analiza oddaljenih klicev (RPC) v distribuiranih sistemih predvsem v smislu performans.

show abstract

Section: Third Generation Rpcs and Web Servicesmentioning

confidence: 99%

Analysing RPC and Testing the Performance of Solutions

Király

Szekely

2018

IJCAI

View full text Add to dashboard Cite

show abstract

“…This module can strip out the headers, parse the data (if needed), and call any other functions or modules as needed. [12,3] 3.1. XML-RPC XML-RPC was designed in 1998 as an RPC messaging protocol for serializing procedure requests and responses into human-readable XML.…”

Section: Third Generation Rpcs and Web Servicesmentioning

confidence: 99%

Some aspects of using RPC

Király¹,

Székely²,

Király³

et al. 2018

Proceedings of the 10th International Conference on Applied Informatics

View full text Add to dashboard Cite

In a client-server network, sockets provide a mechanism for a program to establish a connection to another program and send messages back and forth. This interface underlies the working of a mechanism that allows a program running as a process on computer A to call a procedure or a function on computer B, pass parameters to it and have the result returned. After the call, the caller process on A is suspended and execution continues on B. When the callee procedure or function on computer B finishes and produces its results, it is passed back to the calling environment on computer A. Then the process on A continues the execution from where it was suspended. This mechanism is called the Remote Procedure Call (RPC). The question is how long must the process wait for the answer to arrive from computer B and why? To answer the question, this paper describes the structure of third generation RPCs and analyses them, putting the focus on the way of marshalling parameters, and performance. To facilitate the choice between them this paper represents the results of performance tests carried out by the authors. The tests are implemented in Java, Ruby, and C++ using GRPC, XML-RPC, and JSON-RPC with calls between the languages to create a broader picture of their performance characteristics.

show abstract