4 ms·
The big problem is that rpcgen is hairy and not reeeeeeally portable (in my experience, if there's a feature you want, it's not supported on your Unix). XDR is
by i80and 10y ago
The big problem is that rpcgen is hairy and not reeeeeeally portable (in my experience, if there's a feature you want, it's not supported on your Unix).
XDR is nice, though, apart from being big-endian and not having widely-supported 64-bit integers. It's a pity it's unfashionable.
- cdegroot 10y agoI think I re-implemented rpcgen a couple of times in Ye Olde Days, so it can't be hard. Then DCE came by and then I lost track of serialization protocols that are essentially rehashes of SunRPC/XDR. So yeah, I've been thinking along the same lines as Scott - why? These days, I've mostly thrown the towel and plunk in JSON everywhere. At least it's hip, and if I ever find a piece of code where the serialization is the bottleneck, early enough to start pushing XDR (not ASN.1 - I once tried to write a parser for _that_ and ended up with some extra grey hairs ;-)).