19 Jun
2015
19 Jun
'15
2:06 p.m.
2015-06-19 14:55 GMT+03:00 Michal Privoznik <mprivozn@redhat.com>:
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.
Thanks, i'm try to create parser for src/remote/remote_protocol.x to generate payloads struct. -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru