Networking - RPC on the server

Unity Engine
1

I’m building a list of the players connected on a host, with a button in front of each player to get extra info about them.
So basically I need to do a round-trip: the client asks (via RPC) the info on player X, the server receives the RPC and sends back another one with said info, and finally the client receives the info he wanted.

This all works… except on the host! When I make a RPC call with RPCMode.Server, it’s just ignored.
Is that expected behavior or bug?

So a), I need to check on both end of the round-trip if Network.isServer, and use RPC or SendMessage accordingly. Messy.
And b), I can’t SendMessage with more than one argument (which I need to), so it’s even messier, I have to implement a complete second logic. All this for one simple round-trip.

Now why the hell can SendMessage only use one argument is beyond me, even RPC() is better at this game! I won’t even mention Invoke, which takes no argument.

2 
This all works... except on the host! When I make a RPC call with RPCMode.Server, it's just ignored.
Is that expected behavior or bug?

RPCMode.Server only does a remote procedure call and not local execution. Thats the way its set up right now. To do what you want to do:

networkView.RPC("SomeFunction", RPCMode.Server, parameter1, parameter2);

becomes

if (Network.isServer)
    SomeFunction(parameter1, parameter2);
else
    networkView.RPC("SomeFunction", RPCMode.Server, parameter1, parameter2);

If the function is in another object couldn’t you reference that object directly instead of using SendMessage and thus avoid changing the target function? Like someObject.SomeFunction(etc, etc).

3

Yes, my function is indeed in another object, that I can reference… in this case.
But I wanted to point out that it’s a pity to have to break the code model just to adapt for the case of the host, while it works for everyone else.
Maybe you could make an overload of the RPC function for this “also send to myself” case…? Maybe it could even be a parameter of the [RPC] attribute.

On a more general subject, I find it super-cool that RPC accepts more than one parameter, but it also reveals how sad it is that SendMessage doesn’t.
Is there any technical limitation to that? I really can’t see why there would, since you can do it with RPC, so…

Also, I tried to make overloads to keep the code closer to the original model, like:

	[RPC]
	void SendPlayerInfo(NetworkPlayer requester, int playerID)
	{
		// this is sent via RPC
	}
	void SendPlayerInfo(int playerID)
	{
		// this is called directly via a reference
	}

This way I can always use the same call model, or even make a helper that would automatically do something like:

	if (Network.isClient)
		networkView.RPC("SendPlayerInfo", RPCMode.Server, Network.player, playerID);
	else
		SendMessage("SendPlayerInfo", playerID);

(I didn’t work out everything yet but you get the idea.)

… but it doesn’t work because I get a “wrong number of parameters” exception, for both RPC and SendMessage.
So I suppose that they call the first available overload, without checking the parameter types.

So I’m wondering, how do SendMessage and RPC work exactly? Are you using Reflection, or is it some sort of faster but more limited internal implementation?
Because with Reflection I know how to find the correct overload depending on the parameters, and could, I think, implement some sort of more generic SendMessage, but I’m just worried it would be too slow to use… or would it?