> On Nov 8, 2014, at 8:01 AM, Matthew Ahrens <[email protected]> wrote:
>
>
> FYI - Long term, we'd like the kernel to do more of the property processing,
> so this could eventually turn into simply:
> - do an ioctl to get the requested properties of the requested datasets,
> returning an nvlist
> - print nvlist as json (which has already been implemented, e.g. by Joyent)
Is there an intent that the kernel do JSON encoding (or decoding)?
Ultimately, I think this is best done in userland, as there are other formats
than JSON that are interesting (e.g. msgpack), and JSON’s inability (per spec)
to encode everything that might in our nvlist’s (specific numeric types,
especially 64-bit integers) is kind of annoying.
- Garrett
>
> There are going to be a couple of talks about how this might be achieved at
> the OpenZFS Developer Summit on Monday, you might want to catch the live
> stream (or recordings will be posted later in the week).
>
> (However, that long-term plan doesn't mean we shouldn't in the mean time do
> JSON printing with the current infrastructure, as you're proposing.)
>
> --matt
>
_______________________________________________
developer mailing list
[email protected]
http://lists.open-zfs.org/mailman/listinfo/developer
