Understanding the Need for Database Publishing - HTML

As previously discussed throughout this book, pure HTML documents tend to be very static, offering little to no dynamic content. Consider the following examples:

  • An order form presented with straight HTML cannot properly represent the vendor’s stock levels, potentially allowing customers to order more product than can be shipped.
  • An online newsletter must be manually assembled and edited in HTML. Furthermore, such online content cannot be easily searched or presented in multiple formats.
  • Customer records, historical data, and so on cannot be manipulated, searched, or validated against other data.

However, when your documents can interact with database content, you can easily mitigate the concerns mentioned in the preceding list:

  • The order form can represent the current stock level, alerting customers to backordered items and potential ship dates. The form can also look up shipping estimates and tax rates where applicable.
  • The online newsletter can be edited piecemeal and assembled by running database queries against a database holding massive amounts of content. The content (even historical content) can be represented in many forms and searched for specific content.
  • Data can be stored, retrieved, validated, and otherwise manipulated.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

HTML Topics