In this chapter, we present the overall architecture of our system that includes Web 2.0 Toolbar and Web 2.0 Management and then introduce each component in our system. Additionally, in the last subsection, we describe the sequential flow in our system.
3.1 Overall Architecture
Figure 3-1 System Architecture
In regular HTTP transaction [21], the User Browser sends a HTTP request to the
the architecture of the traditional HTTP transaction, we append another two components: Web 2.0 Toolbar and Web 2.0 Management to become the new architecture. Figure 3-1 illustrates the new architecture we proposed with the communications of every component.
In the aspect of the user, when the User Browser sends a HTTP request to the Original Web Server, Web 2.0 Toolbar can obtain the URL of this HTTP request and ask the information which related to the original web page from Web 2.0 Management.
By this way the User Browser not only receives the original web page form the Original Web Server but also gets the information related to this web page. Hence, the user will see a new view of Web 2.0 web pages which include original contents and additional services (which indicate tagscommentschat room and RSS).
In the aspect of the Website Developer, the Original Website and additional services seem be built together but can be managed separately. The Website Developer registers to Web 2.0 Management and takes over the information (tags and comments) related their websites. Web 2.0 Management supports Website Manager to allow these Website Developers to create and delete tags/comments.
The Web 2.0 Toolbar framework has two main components: Web 2.0 Toolbar and Web 2.0 Management. The detail descriptions of them are in following sessions.
3.2 Web 2.0 Toolbar
The relationship of the User IE Browser and the Original Web Server is a client/server model, and the one of Web 2.0 Toolbar and Web 2.0 Management is similar to another. Web 2.0 Toolbar not only plays the role of client in the mode but also acts as a coordinator between User IE Browser and itself. There are three major
works which Web 2.0 Toolbar deals with. First it demands the URL of the web page which User IE Browser is handling with. Second it communicates with Web 2.0 Management. Send the URL from User IE Browser as parameter to Web 2.0 Management and take the relevant information back. Third Web 2.0 Toolbar integrates the original web page and the additional relevant information together. Accurately to say, Web 2.0 Toolbar appends the additional data to the original html page. The detail implementation will be interpreted in Chapter 5.
3.3 Web 2.0 Management
Web 2.0 Management contains four subcomponents: Web 2.0 ServerData ServerManager Server and Ping Server. All of them are illustrated in Figure 3-2.
Figure 3-2: Web 2.0 Management
Data Server contains two parts, Web 2.0 DB and Data Processor. Web 2.0 DB is a database to store all entries of the web page and other relevant information. It supports all data which the system needs. Data Processor has the knowledge of both the object representation and the database schema. It supports an interface to access Web 2.0 DB for the other three subcomponents. Data Processor and Web 2.0 DB have keen sense of responsibility to manager all data.
Web 2.0 server is a HTTP web server, and it consists of four parts, Tager CommenterChater and RSS Manager. We will introduce them one by one. Tager supplies three functions which are creatingrating tags for each web page and viewing these tags and their rates of each web page. Tager processes the related data by Data Processor and delivers them to Web 2.0 Toolbar. The work of Commenter is quite similar as Tager, but the only different point is that Commenter processes comments not tags. Chat supports only one function. That is the users who are viewing the same web page can talk to each other. That means every web page additionally supports a chat room function, and everyone can discus the content of the web page very friendly.
RSS Manager is a very simple RSS reader. It allows the user who has already registered to subscribe/delete some RSS feeds. Once these feeds have updated, RSS Manager will send the notices to these users.
Ping Server was built for supporting RSS Manager. It continues to check if these RSS feeds have an update or not. Once an update happened, it will modify these related data in Web 2.0 DB by Data Processor.
Manager Server supports the Website Developers who have already registered to our system to manage the related information. Website Developers can create/delete the tags and comments related their web pages. Building more suitable data to their websites, and reduce these incorrect or abusive data.
3.4 Sequential Flow
Figure 3-3: A flow of using Web 2.0 Toolbar
The Figure 3-3 illustrates the sequential flow which a user is using Web 2.0 Toolbar. The scenario contains five steps, and we will explain them as follow:
Step1: A user types a web page URL on the IE Browser, and the User Browser sends a HTTP request to Original Web Server and gets the Web page response content.
Step2: the user clicks the tag button to using tag service. Step3: Web 2.0 Toolbar sends a request to query the URL of the web page and obtains the response value.
Step4: Web 2.0 Toolbar sends the HTTP request of the tag web page to Web 2.0
tag web content into User IE Browser. The other services are similar to this flow. The difference between them is that it returns the corresponding web content rather than tag web content.