Re: [libvirt] libvirt proxy

As Dan says, I too discourage you from doing this. But if you really need to dig into RPC, then: 1) payload is just function arguments serialized. In general, two functions have different set of arguments, and therefore different payloads. 2) The (de-)serializers are generated from .x files, e.g. src/remote/remote_protocol.x 3) There's a wireshark plugin under tools/wireshark/, you may want to check it out. But it's mainly for developers - to see the data passed through RPC tube.