The goal of the application is to organize, publish, and preserve files. A Data Grid is the software infrastructure that maps from access mechanisms provided by grids to management functions provided by the application. An analysis of how the application can be implemented based on data grids will identify whether functionality is missing from current grid services.

The challenge in managing information flow is that coordination is required between services. When individual files are uploaded, it may be appropriate to do processing at the remote storage location for some of the meta data. Also, when the files are downloaded, it is needed to record the data about the frequency of downloading for analysis. The user information is supposed to be stored at the client side. At each downloading of files, the relevant information of the downloading must be recorded in terms of the date and identifier in the grid

The above picture shows the data grid model of this system. A normal end-user starts with providing the resources name he/she wants. This means a request will be sent to find if the resource does exist in the grid. The physical location and name of the requested resource file will be returned if the file existed. The relevant information about the resource file will be returned as well and they will be displayed on the user side. The user can then decide to download the file. Once the file is downloaded, more data are generated, which is the date when the file is being downloaded.

Any organization or individual can contribute data storage for the grid. First they need to register at the Resource Contributor Server. When anyone wants to upload or share large volume of files, they need to connect to the Resource Contributor Server. The Resource Contributor Server will be responsible for allocating storage for the shared files. Everyone can browse the resources or search the files at the client side. Figure 2 shows different layers of components in this system

home>>