diff options
| author |   Marek Gradzki <mgradzki@cisco.com> | 2017-12-07 15:40:11 +0100 |
|---|---|---|
| committer |   Damjan Marion <dmarion.lists@gmail.com> | 2017-12-09 13:23:15 +0000 |
| commit | 6e73f7f6055a9ba1c4e604060934a0aa5e555f57 (patch) | |
| tree | 84ad8d53635552c1a158d48d783b794f34e1d762 /src/vpp-api/vom/l3_binding.cpp | |
| parent | c42fc05bfbb26fd11fe92ac9d11587660a817ac1 (diff) | |
jvpp: do not hardcode event sufixes (VPP-940)
JVpp maps request messages with replies
for Java API user convenience, e.g.:
- do not polute send APIs with messages other than requests/dumps,
- allow callback registration only for replies/details and events.
Since there are no conventions for event message naming
(https://wiki.fd.io/view/VPP/API_Concepts#API_Conventions),
jvpp should not limit events to messages
that end with 'event' or 'counters' suffix.
Instead jvpp should treat all messages
except for requests/dumps as potential events.
Such behaviour was introduced on Java API level by
https://gerrit.fd.io/r/#/c/8377/
in order support reusing
details messages as events (e.g. BFD events).
This patch goes one step forward by
relaxing rules at jvpp generation level.
Change-Id: I2a35e9eb2a288b2cf02d36ca95e6cb13e76e19e3
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
Diffstat (limited to 'src/vpp-api/vom/l3_binding.cpp')
0 files changed, 0 insertions, 0 deletions