This is the first module I've ever built that seems to have enough generic applicability that I'm going to upload it to CPAN. I'd like to get some feedback here on PM before publishing it to CPAN, especially on the namespace of the module. It implements an efficient and fairly advanced pre-forking tcp network server in C with callbacks to perl for module users. It will not work on anything but Linux, and beyond that requires perl 5.8.1+, kernel 2.4+, glibc 2.2.5+, and gcc 3.1+. Any feedback welcome.

The module tarball as I expect to send to it CPAN prior to any changes picked up from feedback here is currently downloadable from: http://www.dtmf.com/Linux-TCPServer-0.16.tar.gz

The largest issue at the moment (aside from the usual: finding and fixing any bugs, and best practices in terms of module file layout and documentation, etc) is the module's name. In perusing the CPAN modulelist, it seems like a ^Linux:: name is appropriate (of the 23 modules with linux in their names, only one is outside of ^Linux::). One monk who might well know better than me has suggested that it should perhaps be more of the forms TCPserver::Linux or Net::TCPserver::Linux.

I was also considering Linux::Net::TCPServer, but for some irrational reason that seems to imply to me that it's for networking between Linux machines only, which isn't true (it only runs on Linux, but it will communicate with anything). . . . ? ? ?

UPDATED Dec 15 2005: New version 0.16 is out, just in case anyone was watching this dead space :) , name still hasn't changed yet. I honestly feel a bit trapped by the whole naming issue. On CPAN, It doesn't belong where it fits and doesn't fit where it belongs, but I think it's useful and I'd still like to stick it out there, and I really don't forsee myself having the desire or time to add UDP support.

In reply to RFC - Linux::TCPServer (new module) by ph713

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.