Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Well it all depends on what type of usage you are expecting. If the pages are viewer agnostic, (No: Hi Lee! Welcome Back.) I would go static and generate the page when they actually update the record. If they are doing this from an app you are making, it should be trivial to catch changes.

If there's no real process (just using mysqladmin or something) You could run a query every couple of minutes and compare the timestamps to a "published" timestamp to see if it needs updating. Much simpler and less fragile. The less parts there are, the less parts there are to break IMHO. If you need real time inventory or similar embedded in the pages and they change constantly, then live is certainly the way to go.

As far as linkage, I would just make the id (page name) always the $product_code=~s/\W/-//g; $product_code =lc( $product_code . '.html'); Then there isn't any confusion on how to link to something. You could even "borrow" the bracketed linkage from perlmonks for internal links in the raw data and it would be simple to check the validity of local links when updating.

Personally, we use static pages for 95% of our work.

-Lee

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

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

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



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (5)
As of 2024-03-29 02:36 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found