Consider the following scenario, which illustrates the value of this information. A user has a Tungsten T, which is a Palm OS 5 device. This device comes with a browser called Web Pro, made by Novarra. The Web Pro browser uses a proxy server, and the proxy server helps make HTML pages digestible to the Web Pro browser. Either the Web Pro can use normal HTML, with frames and the like, or it can use simple HTML. When the user uses the Web Pro browser to visit WebAccess using the simple HTML templates, the performance is much better than when using the regular HTML/Frames templates. When the user first used GroupWise WebAccess with the Web Pro browser, the performance was very slow. You then instructed the user to change the URL on the Web Pro browser to indicate to WebAccess that the device was using a simple HTML browser. The WebAccess session's performance becomes much better. Following is the syntax the user used to force the WebAccess Application to serve up simple HTML: http://groupwise.wwwidgets.com/gw/webacc?User.interface=simple Typing this long URL once and then bookmarking it is not too difficult, particularly for a technical person. But imagine you have a bunch of users who want to access GroupWise WebAccess from their Tungsten T. Wouldn't it just be better to have GroupWise WebAccess detect the Web Pro browser type, and then give the users the simple HTML templates automatically? Of course. So here's how you can do this:
If a web browser identifies its Browser User Agent information with a string that contains WebPro, the WebAccess application uses simple HTML templates. You must stop and restart the web server and the Java servlet gateway that are hosting the WebAccess application for these changes to take place. |