+1 :)
>From the 'consumer of api' side... the 'catch all' nature of vpe.api makes
VPP less usable. Proper modularity would improve that, and be a benefit
beyond the ones Damjan already mentioned.
That said, ccing the some of the GoVPP folks, because there are some
(hopefully quite tractable) iss
Guys,
Can we get a rid of vpp/api/vpe.api and vpp/api/vpe_types.api by moving content
to more
appropriate places. I.e. some basic types and control_ping may be good
candidate for vlibapi/.
It is quite weird that we have dozens of plugins depending on header files
autogenerated from the main
