March 2007
Intermediate to advanced
326 pages
9h 3m
English
As application architects and designers, we like dynamic content on the web. It’s more interesting than static content, for one thing. For another, nobody needs programmers to put up static content. We even have a derogatory term for it—brochureware. When the requirements state that the content can change at any time, we tend to accept that and immediately jump to a database-driven, dynamically generated site. All of the common technologies drive us in that direction: JSP, ASP, Ruby on Rails, and so on.[75]
The trouble comes from that multiplier effect again. Consider a typical retail site. Almost every retail site allows ...
Read now
Unlock full access