182 CHAPTER 6 (Web hosting unlimited bandwidth) DECOUPLED NAVIGATION PATTERN Figure
182 CHAPTER 6 DECOUPLED NAVIGATION PATTERN Figure 6-15. Component architecture exposed as URLs In a nutshell, URLs begin with a general functionality definition and with each appended identifier to the URL the functionality becomes more specific. The URL /search is general, but the URL /search/impl/amazon is specific. The URL /searchimplements a searching component, whereas /search/impl/amazon relates to a search component specific to Amazon.com. This way of creating URLs is purely resource and state driven, and will conflict with those web appli cations that map directory structures to URLs for organizational purposes. Referencing URLs in HTML Pages E B V N When referencing a URL in an HTML page, do you really know what the URL is or should be? It has been explained that URLs should be components, but how are those components discovered? Consider the following link: Amazon Implementation What does the URL /search/impl/amazon represent philosophically? How do you know that the Amazon.com implementation is at the URL /search/impl/amazon? Even more direct, how do you manage to download the content that references the URL in the first place? There is a German saying, You can t smell it, which means that something needs to be defined somewhere because a URL does not have an odor to guide you to the proper location. One way to define the URL is to use a JSP or ASP.NET page that generates the URL as follows: Domain Name Hosting services for high quality webhost to host and run your jsp applications.