pure transit server

[Fabien Tassin]

According to Russ Allbery:
> 
> BTW, if you do write a pure transit server, I for one would be happy to
> see about having it be part of the INN package....

I've converted quite easily my server to be multi-threaded. Lets call this
beast "inntd" for InterNetNews Transit(er?) daemon. I wanted to directly
use INN history and CNFS code but I don't think they are thread-safe.
I've first looked at the CNFS code but, ootch, how dense and fuzzy ! APIs over
APIs, conf files over conf files. I'm currently looking at the dbz code
but like CNFS and anything that can be useful for me, it is too tied
to libinn, autoconf and the like. Don't know what it is better, fighting
with current code or rewriting everything from scratch. I want to avoid
to fork a new project but it is probably simpler. Ideas ?

About threading, I'm using Linux pthreads. I try to write portable code
(I'm not using autoconf yet) but threads are always a problem.
Thoughts ?

-- 
Fabien Tassin -+- fta at sofaraway.org