Thank you very much for your reply.

Indeed, I did not know about modulinos. This technique is very interesting. It seems that it resembles the way I have done it now (see above).

Regarding the frameworks: I admit that I don't like them very much because most of them are not flexible enough for what I want to do, or the learning curve is very steep. Every time I tried a framework or read the documentation of a framework, I have come to the conclusion that it would take more time to learn the tricks to break its limitations than the framework would save, or that the framework's philosophy was not mine.

To make a long story short: Frameworks are not appropriate for me. I am very happy with putting my well-tested methods in several modules and use these modules from my applications.

By the way, the same applies for the template systems. I have written my own template system which might not be appropriate for the mass market, but is very simple and just does what I want, thereby keeping maximum flexibility (i.e. I can write pure perl code without any restrictions in my HTML pages).

Since your answer contains some very interesting hints, I have voted it up, although I have chose another solution.

Regards,

Nocturnus

In reply to Re^2: How to pass form data from a CGI script to its child process? by Nocturnus
in thread How to pass form data from a CGI script to its child process? by Nocturnus

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.