The point is that if I have the server use NSArchiver to encode an
invocation, send the resulting data, and then use NSUnarchiver to
reconstruct the invocation on the client side, then I would have to
invest some effort to obtain NSDistantObjects corresponding to the
invocation's object arguments on the client side.

> All that information is crammed into the method's signature. It has a
> bunch of private methods you may be interested in.

I realize that I can parse an invocation's method signature to encode
and decode the invocation, but doing so would require significant
effort (to accommodate non-object arguments) and would presumably
replicate what has already been done for NSPortCoder. Thus my
original interest in whether it is possible to tweak NSPortCoder and/
or NSSocketPort to use a socket configured for multicast...