On Wed, Apr 11, 2018 at 02:32:29PM +0200, Matthias Schiffer wrote:
> I plan to use libnftnl directly. If removing parts of the API from libnftnl
> is acceptable at this point, moving all parts in libnftnl dealing with
> human-readable or JSON input/output to libnftables would be an alternative
> to splitting another library out of libnftnl.

Assuming that libnftables is the only user of libnftnl we do care about,
I guess if it can live without the printing routines from libnftnl there
shouldn't be a problem in dropping them.

So I just had a look at where libnftables prints nftnl objects:

* Netlink debug output.
* Monitor output if JSON output is requested. (Actually also for XML
  output, but libnftnl doesn't support that.)
* Export command.

My implementation should replace the latter two completely, so
everything boils down to finding an alternative for netlink debug
output. Maybe it is possible to go with a more generic approach
(something like a semi-intelligent hexdump or so) so we don't have to
keep custom printing functions for every possible nftnl type?

Ideas anyone?

Cheers, Phil
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to