nDPId/schema
Toni Uhlig f9bd7d29ce
Bump libnDPI to 37f918322c0a489b5143a987c8f1a44a6f78a6f3 and updated flow json schema file.
* export env vars AR / CMAKE_C_COMPILER_AR and RANLIB / CMAKE_C_COMPILER_RANLIB while building libnDPI
 * nDPId check API version during startup (macro vs. function call) and print a warning if they are different

Signed-off-by: Toni Uhlig <matzeton@googlemail.com>
2022-09-06 14:50:46 +02:00
..
daemon_event_schema.json bump libnDPI to 8f6a006e36eef0ae386f7e663d3ebecfad6a2dc9 2022-07-01 13:50:53 +02:00
error_event_schema.json Renamed basic event to error event for the sake of the logic. 2022-03-13 03:08:44 +01:00
flow_event_schema.json Bump libnDPI to 37f918322c0a489b5143a987c8f1a44a6f78a6f3 and updated flow json schema file. 2022-09-06 14:50:46 +02:00
packet_event_schema.json bump libnDPI to bb12837ca75efc2691ecb18fd5f56e2d097ef26b 2022-03-24 02:16:33 +01:00
README.md Updated README.md 2021-03-24 14:44:27 +01:00

schema

All schema's placed in here are nDPId exclusive, meaning that they are not necessarily representing a "real-world" JSON string received by e.g. ./example/py-json-stdout. This is due to the fact that libnDPI itself add's some JSON information to the serializer of which we have no control over. IMHO it makes no sense to include stuff here that is part of libnDPI.