Re: [**EXTERNAL**] Re: [vpp-dev] VPP client: test_client vs VAT

2018-04-09 Thread Dave Wallace
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 app

Re: [**EXTERNAL**] Re: [vpp-dev] VPP client: test_client vs VAT

2018-04-08 Thread Ole Troan
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 wou

Re: [**EXTERNAL**] Re: [vpp-dev] VPP client: test_client vs VAT

2018-04-08 Thread Jim Thompson
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/RES

Re: [**EXTERNAL**] Re: [vpp-dev] VPP client: test_client vs VAT

2018-04-08 Thread Gudimetla, Leela Sankar
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

Re: [vpp-dev] VPP client: test_client vs VAT

2018-04-08 Thread Jim Thompson
> On Apr 8, 2018, at 7:00 PM, Gudimetla, Leela Sankar > 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. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this grou

Re: [vpp-dev] VPP client: test_client vs VAT

2018-04-08 Thread Gudimetla, Leela Sankar
lace , "vpp-dev@lists.fd.io" Subject: Re: [**EXTERNAL**] Re: [vpp-dev] VPP client: test_client vs VAT Thanks Daw for the response. I think I understood now. The test_client is a good reference point to start implementing the client in my application. Thanks, Leela sankar From: Dave

Re: [**EXTERNAL**] Re: [vpp-dev] VPP client: test_client vs VAT

2018-04-06 Thread Gudimetla, Leela Sankar
**EXTERNAL**] Re: [vpp-dev] VPP client: test_client vs VAT Leela, VAT is an integral part of the Continuous Integration testing infrastructure so that is NOT appropriate to extend for your application. However, it does offer a good set of example code on how to implement a VPP client using

Re: [vpp-dev] VPP client: test_client vs VAT

2018-04-06 Thread Dave Wallace
Leela, VAT is an integral part of the Continuous Integration testing infrastructure so that is NOT appropriate to extend for your application.  However, it does offer a good set of example code on how to implement a VPP client using the binary API. Depending on what your application does, yo

[vpp-dev] VPP client: test_client vs VAT

2018-04-05 Thread Gudimetla, Leela Sankar
Hello, I am trying to implement a client to VPP in my application that configures VPP by calling its APIs. I see that VAT (VPP API TEST?) already has a client implemented as part of its testing infrastructure. And I also see that there is a test_client which is a straight-forward and organic cl