Hi everyone From my experience from using vpp apis in honeycomb,i would like to see approach that api does not use giant ammount of parameters(ip_add_del_route for ex.), specialy if that api call defines more than one logical entity,of if there is too many combinations of use of that api. It allows way better integration(binding code is not that ugly) with standardized models from ietf. This approach can be seen for example in Lisp plugin, where basicaly per logical node from model, there is an api call to write/dump it
Jan Srnicek Engineer - Software jsrni...@cisco.com Tel: Cisco Systems, Inc. Slovakia cisco.com Think before you print. This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Please click here for Company Registration Information. -----Original Message----- From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Neale Ranns (nranns) Sent: Monday, June 5, 2017 12:25 PM To: vpp-dev <vpp-dev@lists.fd.io> Subject: [vpp-dev] VPP API improvements - community discussion. Dear VPP community, Some of the feedback we get from users of VPP is that the client-side API is not particularly user-friendly – we would like to address this. Naturally ☺ In order to create an API that the user community considers effective, easy and intuitive to use, it must be a community wide discussion. To kick-start that discussion, and to provide some initial focus on the specific topics, the document below outlines a set of proposals that we hope moves us in this direction. https://docs.google.com/document/d/1FDXKusKwuHeEP8WU5m3FuRSdzD9zVRgB7BEme-BP0gg/edit?usp=sharing please let us know any opinions you have on this topic, or feedback, suggestions, additions, etc to the document, either by replying to this thread, unicasting me, or by adding comments directly to the document. Thanks in advance, Neale _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
