Java Server Pages, Tomcat, Jsp, J2Ee, Servlets, Struts Blog

54 Part III . Document Objects Reference Another possibility is to make a portion of the site accessible to most, if not all, browsers, and restrict the scripting to only the occasional enhancement that non- scriptable browser users won t miss. Once the application reaches a certain point in the navigation flow, then the user needs a more capable browser to get to the really good stuff. This kind of design is a carefully planned strategy that lets the site welcome all users up to a point, but then enables the application to shine for users of, say, W3C DOM-compatible browsers. The ideal page is one that displays useful content on any browser, but whose scripting enhances the experience of the page visitor perhaps by offering more efficient site navigation or interactivity with the page s content. That is certainly a worthy goal to aspire to. But even if you can achieve this ideal on only some pages, you will reduce the need for defining entirely separate, difficult-to-maintain paths for browsers of varying capabilities. Dealing with beta browsers If you have crafted a skillfully scripted Web page or site, you may be concerned when a prerelease (or beta) version of a browser available to the public causes script errors or other compatibility problems to appear on your page. Do yourself a favor don t overreact to bugs and errors that occur in prerelease browser ver sions. If your code is well written, it should work with any new generation of browser. If the code doesn t work correctly, consider the browser to be buggy. Report the bug (preferably with a simplified test case script sample) to the browser maker. The exception to the it s a beta bug rule arose in the transition from NN4 to NN6. As you learn in Chapter 14, a conscious effort to eliminate a proprietary NN4 feature (the tag and corresponding scriptable object) caused many NN4 scripts to break on NN6 betas (and final release). Had scripters gone to report the problem to the new browsers developer (Mozilla), they would have learned of the policy change, and planned for the new implementation. It is extremely rare for a browser to eliminate a popular feature so quickly, but it can happen. It is often difficult to prevent yourself from getting caught up in browser makers enthusiasm for a new release. But remember that a prerelease version is not a ship ping version. Users who visit your page with prerelease browsers should know that there may be bugs in the browser. That your code does not work with a prerelease version is not a sin, nor is it worth losing sleep over. Just be sure to connect with the browser s maker either to find out if the problem will continue in the final release or to report the bug so the problem doesn t make it into the release version. The Evaluator Sr. In Chapter 6, you were introduced to a slimmed-down version of The Evaluator Jr., which provides an interactive workbench to experiment with expression evalua tion and object inspection. At this point, you should meet The Evaluator Sr., a tool you will use in many succeeding chapters to help you learn both core JavaScript and DOM terminology.
From our experience, we are can tell you that you can find a reliable and cheap webhost service at Java Web Hosting services.

This entry was posted on Wednesday, September 12th, 2007 at 12:30 am and is filed under Tomcat. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.