So having time between sending my mail and receiving this I've just been using the existing on the wire format that was already present in the previous code.
I don't think it'll be hard to convert, but I noticed a couple things which brings me to 2 more questions: - VAPI seems to redefine all the structures. This makes the porting effort harder, why is vapi redefining all the on the wire structures? - VAPI seems to require callbacks for results. The existing code allows for synchronous API calls w/o having to define callbacks for the results. Having callbacks with synchronous calls is pretty cumbersome, is there a way around having to use callbacks with VAPI? Thanks, Chris. > On Feb 18, 2020, at 6:22 AM, Ole Troan <otr...@employees.org> wrote: > > Christian, > > I would recommend using the auto-generated C language binding (VAPI), instead > of directly interacting with the on-wire format. > > Cheers, > Ole > >> On 17 Feb 2020, at 15:10, Christian Hopps <cho...@chopps.org> wrote: >> >> Hi vpp-dev, >> >> I'm working to get strongswan IKE working with VPP, I've found some code on >> github that was doing this as PoC for vpp 18.10. The code is using vl_msg_* >> calls, and handling various duties to manage this API connection. >> >> I also see there is this vapi code in the current VPP. Would it be >> recommended to switch over to vapi instead of this lower level vl_msg* code? >> >> I was hoping the answer would be obvious from looking at the code, but I'm >> uncertain since I see things in the strongswan code like handling thread >> suspend, read timeout and thread exit conditions that I don't see in the >> vapi.c code. >> >> Thanks, >> Chris. > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15447): https://lists.fd.io/g/vpp-dev/message/15447 Mute This Topic: https://lists.fd.io/mt/71349657/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
