Suggested Site-Wide Modifications

only for RuBoard - do not distribute or recompile

Several of the earlier sections describing the scripts that implement the PseudEcom site have suggested modifications that pertain to individual applications. This section suggests some changes that are more general and affect the operation of the site as a whole.

Modify the boilerplate routine add_boilerplate() to indicate whether the customer currently has a pet shop session open, and to report the number of items in the shopping cart if so. This serves as a reminder that the customer has some unfinished business to take care of that is, to complete the ongoing purchase and send us some money!

You can use your storefront to provide your customers with access to information that is not actually stored on your site. For example, if you want customers to be able to see current stock quotes for your company or for related companies of interest, you can include links that point to one of the stock market sites and trigger quote displays.

In Chapter 5, Writing Form-Based Applications, we wrote a script for collecting product registrations (prod_reg.pl). That was a standalone application. What would it take to integrate it into the PseudEcom site? For example, to make sure the pages that prod_reg.pl presents use the same boilerplate and have the same look as other site pages, what changes would you need to make? More generally, what design principles can you identify that should be followed to make an application integrate more easily into the PseudEcom Web site?

only for RuBoard - do not distribute or recompile


MySQL and Perl for the Web
MySQL and Perl for the Web
ISBN: 0735710546
EAN: 2147483647
Year: 2005
Pages: 77
Authors: Paul DuBois

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net