The implication was that the changes were few - that meant it was possible that even an hourly/daily/whatever timed regeneration might have been sufficient.

A static page would use less resource and we don’t know how many home page hits there are.

I was merely pointing out that the complexity of the solution was perhaps overkill for the situation and just wanted to give the OP something different to think about.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 16, 2015, at 3:49 PM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

Jon

excuse me, but serving a homepage 'on the fly' is much more simple that
introducing
triggers that has to monotor if changes has been made in a given timeframe.

It is raw and it is KISS just to serve the page

On Thu, Jul 16, 2015 at 9:42 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

I was thinking along the same lines Bill. Maybe if it needs to be more
dynamic then combine this idea with a trigger or similar event on the
table(s) in question that would regenerate the static page. From the OP’s
original request it sounds as if anything else is overkill.

Just because we _can_ do fancy things is not a good reason to do them -
particularly when it adds complexity.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 16, 2015, at 3:17 PM, William A. Hansen <whansen@xxxxxxxxxxxxx>
wrote:

I was once asked to design a database application for which the optimal
solution was to buy the user a dozen file cards. Reading the posts makes
me wonder whether we are grossly overdesigning Joe's application.

I have a web site that uses AJAX calls for information that can change
by the second. For another, I used server-side calls to dynamically add
the same header and footer information to the 300+ pages making up the
site. While this worked great, I realized this was overkill for pages that
might change only once a month. I now store all pages in XML format and
run a job once a month or as needed to recreates the web site using an XSLT
transform.

Would this problem be solved by running a daily job that simply
recreates the index file?

KISS,

Bill

William A. Hansen
whansen@xxxxxxxxxxxxx
Manta Technologies Inc.
Toll-free: (800) 406-2682 x 101
Direct: (303) 862-4562
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.




--
Regards,
Henrik Rützou

http://powerEXT.com <http://powerext.com/>
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.