With RPC calls, is serialization a necessisity to get the data back to the calling client?

The most direct way to get the data back to the client is using the return from the RPC. This will involve some kind of serialization, although it might be called something else - e.g. Marshalling/unmarshalling depending on the RPC protocol.

The most direct way to get the data back to the client is using the return from the RPC. This will involve some kind of serialization, although it might be called something else - e.g. Marshalling/unmarshalling depending on the RPC protocol. There are lots of indirect ways to get data back to the client that might be initiated by an RPC, here are a few examples: asynchronous message e-mail RSS feed publish to web page Or the client could initiate a request with one RPC and poll for an answer with separate RPCs.

All of these methods involve some form of data serialization in the general sense (but not necessarily in the C#/Java sense).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.