Leela, I’m not entirely sure I understand your question, but I’ll try to answer.
1) It’s an open source project. If you have a vision to improve it, you can propose same and submit patches. 2) there are implementations of an external API. The FD.io Honeycomb project implements NETCONF/RESTCONF for VPP. https://wiki.fd.io/view/Honeycomb We (Netgate) have implemented a front-end to VPP implementing a CLI, RESTCONF, and connections to configure and exchange traditional control plane daemons for Linux such as Strongswan and FRR. Jim > On Apr 8, 2018, at 10:59 PM, Gudimetla, Leela Sankar <lgudi...@ciena.com> > wrote: > > I don't think I totally get it. > My question was to ask why does anyone need to write 'shared-memory' access > to call the corresponding binary API for each and every feature set that one > is interested in. > If there is a direct client library available, then it would be much easy to > call the direct feature API and get going with this API stuff. > > Could you please throw some light on this? > > Thanks, > Leela sankar > > On 4/8/18, 5:39 PM, "vpp-dev@lists.fd.io on behalf of Jim Thompson" > <vpp-dev@lists.fd.io on behalf of j...@netgate.com> wrote: > > > >> On Apr 8, 2018, at 7:00 PM, Gudimetla, Leela Sankar <lgudi...@ciena.com> >> wrote: >> >> Why does the VPP not provide a client library to access the APIs instead of >> writing code to call each API ? > > src/vpp-api/vom/ is a C++ wrapper. > > > > > > > > > >
