Seminar 5

Yes: consider a replicated object A invoking another (nonreplicated) objectB. If Aconsists of k replicas, an invocation of B will be done by each replica.However, B should normally be invoked only once. Special measures areneeded to handle such replicated invocations.

An important advantage is that separate processes are protected againsteach other, which may prove to be necessary as in the case of a super-server handling completely independent services. On the other hand, pro-cess spawning is a relatively costly operation that can be saved when usingmultithreaded servers. Also, if processes do need to communicate, then us-ing threads is much cheaper as in many cases we can avoid having the kernelimplement the communication.

Assuming the server maintains no other information on that client, one couldjusti?ably argue that the server is stateless. The issue is that not the server,but the transport layer at the server maintains state on the client. Whatthe local operating systems keep track of is, in principle, of no concern tothe server.

It can be strongly argued that this is a stateless server. The important issuewith stateless designs is not if any information is maintained by the server onits clients, but instead whether that information is needed for correctness.In this example, if the table is lost for what ever reason, the client and servercan still properly interact as if nothing happened. In a stateful design, suchan interaction