RPC, Java RMI and Marshaling

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall with Kai
GameKnowt Play
New
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/13

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

14 Terms

1
New cards

What is the purpose of the marshaling procedure?

to encode application layer structures in an external form

2
New cards

What is a gossip protocol?

A protocol where peers randomly exchange messages to achieve, for example, unreliable multicast.

3
New cards

What is meant by time uncoupling in a communication framework?

Sender and receiver need not be active at the same time.

4
New cards

What is meant by space uncoupling in a communication framework?

A sender does not need to know the name or identifier of the receiver.

5
New cards

What is meant by an idempotent operation?

n operation that can be performed several times with the same effect as being performed once.

6
New cards

What is meant by causal ordering in a communication framework?

If a client is delivered two messages m1 and m2, then m1 could not have been sent by someone after having being delivered m2.

7
New cards

How are arguments passed in Java RMI?

remote objects as reference, all other as copies

8
New cards

Which invocation semantic is provided by Java RMI?

at most once

9
New cards

What level of transparency is provided by method invocation in Java RMI?

access and location transparency

10
New cards

If a RPC call with at least once semantics fails, we know that

the call might have been executed at least once

11
New cards

What is given by at least once RPC semantics?

even if a failure occurs the call has been invoked at least once

12
New cards

Why is a remote object passed as a reference and not as a copy in Java RMI?

the object contains a mutable state that should not be duplicated

13
New cards

Can we implement a RPC system with exactly-once semantics in an asynchronous system with non-failing nodes but unreliable networks?

no, we can only achieve at-most-once or at-least-once but not both

14
New cards

What is the difference when an error is reported for an at-least-once and at-most-once remote procedure call?

in the at-least-once case, the call could have been executed more than once