I have a bit of experience with CGI applications. The largest one I have written was around 10,000 lines of Perl.

It was a multi-user product database and order retrieval, tracking and reporting system for a big (now defunct) dot com. I can tell you it was a real trial by fire.

In my experience your methodology will play a big part. Is your application screen based? (One screen does one function) or do certain functions require multiple steps?

What's the nature of the data? What security concerns do you have? What performance concerns do you have?

There's a lot of ways to do it and how will depend on your problem and how you like to approach the problem.

Personally, I haven't found any good books on the subject. From my past experiece I am working on a solution for what I see are the big challenges of CGI without tying the user to rigidly too one way of coding. I posted a node in meditations recently. You may find some of the things I listed as requirements as helpful or at least something to consider.

-Lee

"To be civilized is to deny one's nature."

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.