Re: [vpp-dev] backward PAPI-compatibility

2019-04-30 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io
By the way, I prefer to have default values defined already in .api.json files, for example like this [6]; assuming it does not break language bindings. That way we will have just one kind of backward compatibility, so it will be easier to decide API version bumps. Vratko. [6] https://gerrit.fd

Re: [vpp-dev] backward PAPI-compatibility

2019-04-30 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io
ev Cc: vpp-dev@lists.fd.io Subject: [vpp-dev] backward PAPI-compatibility Hello VPP reviewers. When adding a comment to API flag day document, I have stumbled upon an idea, that is somewhat larger than the document itself. It has to do with a weaker form of VPP backward compatibility, specific to clien

[vpp-dev] backward PAPI-compatibility

2019-04-29 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io
Hello VPP reviewers. When adding a comment to API flag day document, I have stumbled upon an idea, that is somewhat larger than the document itself. It has to do with a weaker form of VPP backward compatibility, specific to clients using Python API (PAPI). Here is the relevant part of the commen