CODEWITHSUNDEEP
javac++rpc
Richeek
Richeek

Reputation: 2220

Remote Procedure Calls

I am doing a Software Engineering course in which different teams are building different prototype subsystems of a big system (different subsystem of F35 Lightning aircraft!).

The problem is that teams can use different programming languages (like C++ and Java) depending upon what they are most comfortable in. However, these subsystems need to be communicating with each other (like radar needs to provide object corodinates to navigation and control). Hence we need to come up with a solution in which different modules can interact in real time.

Someone suggested XML-RPC and hence I was reading about it. After reading it I think it is used in server client architecture. Is this a good way of doing interprocess kind of communication? What are my options?

Any help would be appreciated.

regards, Newbie

Upvotes: 0

Views: 481

Answers (2)

miku
miku

Reputation: 188224

There are a couple of options beside XML-RPC. For a short bullet-point comparison, take a look at:

If your exchange is more data-oriented, Protocol Buffers might be an alternative.

Protocol Buffers are a way of encoding structured data in an efficient yet extensible format.

Personally, I would go for lightweight exchange format or method first since the components are considered prototypes. Something like REST or some custom message passing might be simple enough, yet sufficient.

Upvotes: 2

John
John

Reputation: 2326

If you are already familiar with XML, it can be a reasonable answer. An advantage of XML is that you don't have to worry about how different machines represent numbers. A disadvantage is the time it takes to keep converting numbers to text and back to numbers.

Upvotes: 0

Related Questions