Leela,
Is your question is why isn't the client part of the VPP application itself?
If so, the answer is to separate the control plane from the data plane
utilizing a fast, efficient shared-memory interface.
VPP is a highly tuned, high performance packet manipulation/forwarding
user-space application. Execution of the control plane in VPP itself
will quickly make it a low performance packet manipulation/forwarding
application.
There are already plenty of instances of those applications freely
available ;-)
Thanks,
-daw-
On 04/09/2018 02:10 AM, Ole Troan wrote:
To add to what Jim said.
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.
There are 'direct' client libraries in C, C++, Go, Lua, Python and Java.
e.g. in Python you do:
v= VPP()
v.connect(...)
print v.show_version()
v.disconnect()
What else is it you are looking for?
Cheers,
Ole
