【正文】 頁是很常見的。s browser. Then the Web services exported by Configuration Manager are used by it and Mobile Proxy to access the backend database where user preferences are stored.Fig. 8. The munication between these three ponents3. Detailed design, standards, and interfacesIn this section, we will describe the system design, standards, and interfaces details of the three major ponents in our system and the problems encountered. Also, our solutions to these problems are depicted. The system ponents and their interfaces are shown in Fig. 9.Fig. 9. System ponents and their interfaces.In Fig. 9, we can see that, almost all of the interfaces are iw, . Web interface. Because our system is designed for Web application, the iw interface enables us to develop different system ponents by different programming languages or platforms. Hence, it provides crossplatform munication for system development.. Page TailorPage Tailor is designed to be implemented in JavaScript because of the following considerations. 1. JavaScript was designed to add interactivity to HTML pages. This point conforms to the first objective of this paper, . easytouse, since we can embed the configuration tool in a Web page, so that users can configure their settings directly in the browser. 2. By using JavaScript, we can manipulate a Web page through the DOM interface. DOM provides the interface between the JavaScript and original Web pages. In other words, we can change the appearance of a Web page to reflect the user39。s browser, some actions are performed in the background automatically. First, Page Tailor will connect with Configuration Manager to retrieve the user preferences about this current visited page. If the user has personalized this page before, Page Tailor would retrieve the old preferences, and then use the data retrieved to reconstruct the past, such as blocks that had been selected and their order.On the contrary, if there are no preferences about this page, nothing will happen, of course. The purpose of this action is to help users accelerate the setting time。s preferences. So that the volume of data transmission to a mobile phone could be reduced, and thus reduce the consumption of wireless bandwidth as well.. Automatic mobile Web page content extractionThe content adapting algorithm we proposed can automatically adapt Web pages to mobile devices. Users always only care about a part of the web content. Content adapting applications should provide a function to extract these parts from a Web page.. Research contributionThis paper discusses the problems encountered and our corresponding solutions. The major contributions of this research are listed below. 1. A crossbrowser configuration tool is designed. 2. The web based nature of our configuration tool allows a user to configure the settings from different puters, and requires no preinstallation of any software.3. Blocks in a Web page can be chosen correctly under the premise that the layout of a Web page does not change frequently.4. A web based management interface is provided.5. An automatic algorithm for mobile Web page generation is proposed.. Outline of this paperThis paper is divided into seven sections. The following is a brief description of the content of each section. In Section 2, an overview of the proposed system and its three major ponents are given. In Section 3, the System design details, problems encountered, and our corresponding solutions are illustrated. Furthermore, we discuss our mobile Web page generation algorithm in Section 4. In Section 5, some tests are conducted to evaluate our system. A practical example showing how to make use of the proposed tool to eliminate unnecessary scrolling is also presented. Several related works are discussed in Section 6. Finally, in Section 7, we make the conclusion and discuss about the future work.2. System design. OverviewBasically, the personalizing process in our Web page tailoring system prises two steps (Fig. 1). First, user must specify his/her preferences of a Web page using a PC or laptop. Second, he/she has to configure the browser on his/her mobile device to go through a specially made proxy, which is responsible for adjusting the content of Web pages according to the preferences set in the first step. Two pictures are given below to illustrate separately the relationship between a user, our Web page tailoring system, and a remote Web server (such as ) in each step.Fig. 2 describes the interaction in the first step. When a user enters a URL in his/her Web browser, a HTTP request is sent to (Line 1) the corresponding Web server specified in the URL. After processing the request by the server, a HTTP response is sent back (Line 1). If the user wants to personalize