comment on

You might consider a mixture of live and memorex. ;) Use a caching mechanism like Cache::Cache, CGI::Cache, or Apache::Cache to reduce the server and database load. I don't personally have any experience with any of these yet, but I've seen them discussed in the Monastery and I'll bet merlyn has a column or two that would help.

As far as the easy of linking to the pages, if you are using Apache and can modify its configuration, you might look into mod_rewrite. I've used it with great success in the past to map user- and link-friendly URLs to CGI URLs with complex query strings.

-rattus

__________
He seemed like such a nice guy to his neighbors / Kept to himself and never bothered them with favors
- Jefferson Airplane, "Assassin"

In reply to Re: Database driven web content: live or tape? by rattusillegitimus
in thread Database driven web content: live or tape? by talexb

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.


There's more than one way to do things
	PerlMonks