[Lognorm] liblognorm API changes

[Champ Clark III]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Okay.  I see.  I've had only limited interaction with json-c when
working on a Sagan preprocessor that made external calls (TCP) to a
database (IP/URL reputation database) that returned JSON.  I used
json-c to extract fields Sagan needed.

If I'm incorrect and makes it _less_ complex to deal with,  then I'm
all for it.  From a Sagan dependencies,  it really doesn't add
anything "extra".  That is,  it sounds like you're replacing libee
with json-c.

I guess from here it just requires some testing and proof of concept
code :)

- -- 
- - Champ Clark III (cclark at quadrantsec.com)
  Quadrant Information Security (http://quadrantsec.com)
  Key Fingerprint: 2E56 C2EB 1B25 C517 D5BA 2DCF 5E70 B2F8 0381 878A
  GPG Key ID: 0381878A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQPkjRAAoJENnmXt7Lmc3Kc+gH/0K6UTYtBsUUAP4fWabpP3yk
G7LJWE768AiYRF52gtOLzWBiV3D5CBLRN6xe5C1hzrEf7iqDTaHKb4QEFRctHird
4hABdrj6Oq3IVg70cHqbMesZGVLHwRVvhm2ukKjV5Nj9YfJiJH53kF21dSaiE58s
Ahuygmws8Dkddl8JSwKfbbnD1uaq8GSmU63eBldrNb8xHv0xhyAEDn35tBdoGa/v
LbuO9Z1G1JAGfU/lQ8ubw1J6n5+0DcUBsvruoZwBAjoNnZfZs9Ig3Of5JI2gbjMs
vo8BQz+lYxUmpX8KjnUy4HlFThCnTH6A01n5OPGWB7sobIdJnKb6I0zPtiHXb9A=
=Dqln
-----END PGP SIGNATURE-----