Binary API user can obtain pointer to serialized vpp node graph using get_node_graph, but the vlib_node_unserialize function is not exposed.

Current API is not usable for Java client like Honeycomb for two main reasons:

• Java client is able to access the memory directly only using Unsafe class (rather hacky solution, because it is internal proprietary API that may be removed in a future Java release),
• rewriting vlib_node_unserialize in Java is not an option because the serialization format is not portable across VPP builds - it is stored as vector (vec_header_t) which length can be encoded as either 64 or 32 bit value, depending on CLIB_VEC64 flag.

Providing API for reading vlib_node_t structure (at least the information available using show vlib graph needs to be exposed) could be possible solution.