Thanks a lot Klement.
On Fri, Aug 17, 2018 at 5:36 PM, Klement Sekera wrote:
> Hi Chetan,
>
> I think that in this case it's better to use blocking interface, as you
> are waiting for the events to come.
>
> You can take a look at test/ext/vapi_c_test.c - tests called
> test_stats_1, _2 & _3 dea
Hi Chetan,
I think that in this case it's better to use blocking interface, as you
are waiting for the events to come.
You can take a look at test/ext/vapi_c_test.c - tests called
test_stats_1, _2 & _3 deal with stats - first two show a blocking,
efficient interface, third one is non-blocking, w
Hi Klement,
Thanks for your reply!
The exact problem statement is , we are trying to send some events from VPP
to client app , but client is not able to read those events api messages
until it has some pending requests. So as a work-around we are sending
control ping after few seconds from client
What exactly is the issue? According to vapi_dispatch() docstring this
is expected:
/**
* @brief loop vapi_dispatch_one until responses to all currently
outstanding
* requests have been received and their callbacks called
*
* @note the dispatch loop is interrupted if any error is encountered
o
