I would personally think the thinng that can go very wrong here is the namespace. it sounds to me that your code solves a very specific problem.

Perhals it shold be a script instead?
If you think things here will be re-used.. then yeah.. module.

How will I, as a developer, interact with your module? Does your program/system basically tell me if ssi-exec is forbidden or not? Then I suggest that this is *one* of a set of utilities or helper functions your module should provide.

I can't freak out enough about the Namespace. Depending on what your code does. Do a search on CPAN for ssi, what do we get.. Doesn't seem to be anything about stats. You should look for Server Stats or something like that. I would say Apache.. Is SSI only available on Apache? Seems to me that your functinality fits in with App::Info::HTTPD::Apache.. no?

if that does not do the trick - then write App::Info::HTTPD::Apache::SSI , maybe.

Would I be able to interact with your code like: 

use App::Info::HTTPD::Apache::SSI qw(status);

my $status = status();
print "ssi on? ". $status->{ssi_on};
print "ssi exec on? ". $status->{exec_on};

[download]

What you suggest is interesting. I would love that for suexec etc.. Make the thing real open to what and how it can be asked, and conservative about how it talks back.

In reply to Re: Module Idea by leocharre
in thread Module Idea by pileofrogs

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.