3 ms·
Given Cisco's history of designing and standardizing protocols, I'll consider their RPC protocol over SOAP at any time (even having a cursory knowledge of it).
by huhtenberg 18y ago
Given Cisco's history of designing and standardizing protocols, I'll consider their RPC protocol over SOAP at any time (even having a cursory knowledge of it).
The problem with SOAP is not that it's bloated or that doesn't allow for efficient parsing or whatever the flaw du jour is. The problem is that it's was created, promoted and embraced by people ignorant of established protocol design practices.
If they wanted interoperability, there was an ASN.1 in DER or PER encoding readily available. If they wanted forward compatibility - why not use trivial TLV encoding ? And why the hell would anyone want to use text-based protocol for passing binary data around ? "Easier to troubleshoot" they say. Huh ?! ARE YOU NUTS ? Why not render the data into a .png then and exchange those instead ?
</rant>
So, I really hope Cisco does standardize their protocol. RPC may be a flawed approach to begin with, but at the very least there'll be a decent protocol to utilize this "flawed" technology.