Yeah you're probably right about all of that. The module was written out of personal need, so I guess I've always been coming at it as a user, and thinking in terms of how to best write code that uses the module when I'm writing the documentation. I think I will still keep most of the extraneous detailed stuff in another pod somewhere though. Basically, if your project *really* needs this module, chances are high you're going to want to know all of that stuff if you don't already (the network stuff that is).

Actually, it's not worth making a seperate pod just to rehash socket-related manpages, curious users can figure that out for themselves

The implementation details probably don't matter so much, I may just move them over to comments in the C code.

I think I'll just kill the example in the docs and tell people to read the lib/Net/TCPServer/Linux.pm source for the example. It's basically the same thing minus the database stuff, and it's the default callback implementation that gets used by the test script, etc.

ETA: That exact BWK quote has been in the back of my mind for the past couple of weeks, because I know I've been too clever for my own good in numerous places in the C source of this module. :)