When you are on vacation in Hawaii sipping your Flaming Zombie, the wonderful people back in the office can still edit the "static" contact info, etc. through a web-based editor without having to call you to cut your relaxing week off just to rush back and add the extension onto the zip code! Wouldn't that be swell?!? Not only that, with db apps, you can show other departments/clients how you are "empowering" them with "synergy" and allowing them the ability to be in control of their content. Meanwhile you can make more cool db driven apps and schedule your next vacation.
Scott -----Original Message----- From: Jeff Chastain [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 3:10 PM To: [EMAIL PROTECTED] Subject: RE: Static vs. Dynamic Content? So are we talking about putting everything into the database - i.e. login forms, search forms, plain text content with HTML formatting, etc.??? -- Jeff -----Original Message----- From: Kathryn [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 2:51 PM To: [EMAIL PROTECTED] Subject: RE: Static vs. Dynamic Content? Jeff, We do it for ease of maintainability. By using a db, we can maintain content through a web-based admin module we designed. However, we are a relatively small company and I am only working on our Intranet, so bandwidth/hits on db issues are not issues for me. Kathryn Butterly Web Developer Washington Mutual Finance 813 632-4490 [EMAIL PROTECTED] -----Original Message----- From: Jeff Chastain [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 3:39 PM To: Fusebox List Subject: Static vs. Dynamic Content? Moving this to a new thread ... what are the good vs. bad points of moving all static content to a database? For example, if I wanted to provide a contact page - the way I have been doing it would be to just hard-code the contact information into HTML in the display fuse. I would have a home.contact fuseaction that only had this one display fuse - that way I could make use of nested layouts etc. This contact information is not something that would change frequently, so why waste the bandwidth/processing time to make a hit on the database? Recent discussions (see Indexing a FuseBox Site thread) seem to point towards people storing all of their content in the database. I would like to hear some discussion as to why you would want to do that (other than making it easy to search)? Thanks -- Jeff ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
