My idea is for echld to dynamically link epan after fork()ing the dispatcher from the client process and before initializing epan so that the client process "does not carry" epan and the dispatcher has a pristine initialized epan ready to be fork()ed that does not carry the entire client process' stuff. That's why I believe it should use epan instead of being a part of it.
Originally I wanted it to be a single .c/.h file pair to be statically linked to the client but I think a one file solution would stop being manageable soon.
For the naming of the files you're perfectly right, I'll take care of that in the next commit.
Thanks,
\Lego