This document provides an overview of the various documents and links that are part of this project's general information. All of this content is automatically generated by Maven on behalf of the project.
Overview
| Document | Description |
|---|---|
| About | The OODT grid services (product and profile services) use CORBA or RMI as their underlying network transport. However, limitations of CORBA and RMI make them inappropriate for large-scale deployments. For one, both are procedural mechanisms, providing a remote interface that resembles a method call. This makes streaming of data from a service impossible, because there are limitations to the sizes of data structures that can be passed over a remote method call. Instead, repeated calls must be made to retrieve each block of a product, making transfer speeds horribly slow compared to HTTP or FTP. (Block-based retrieval of profiles was never implemented, resulting in out of memory conditions for large profile results, which is another problem.) Second, both CORBA and RMI rely on a central name registry. The registry makes an object independent of its network location, enabling a client to call it by name (looking up its last known location in the registry). However, this requires that server objects be able to make outbound network calls to the registry (through any outbound firewall), and that the registry accept those registrations (through any inbound firewall). This required administrative action at institutions hosting server objects and at the institution hosting the registry. Often, these firewall exceptions would change without notice as system adminstrators changed at each location (apparently firewall exceptions are poorly documented everywhere). Further, in the two major deployments of OODT (PDS and EDRN), server objects have almost never moved, nullifying any benefit of the registry. This project, OODT Web Grid Services, avoids the prolems of CORBA and RMI by using HTTP as the transport mechanism for products and profiles. Further, it provides a password-protected mechanism to add new sets of product and profile query handlers, enabling seamless activation of additional capabilities. |
| Continuous Integration | This is a link to the definitions of all continuous integration processes that builds and tests code on a frequent, regular basis. |
| Dependencies | This document lists the project's dependencies and provides information on each dependency. |
| Dependency Convergence | This document presents the convergence of dependency versions across the entire project, and its sub modules. |
| Distribution Management | This document provides informations on the distribution management of this project. |
| Issue Tracking | This is a link to the issue management system for this project. Issues (bugs, features, change requests) can be created and queried using this link. |
| Mailing Lists | This document provides subscription and archive information for this project's mailing lists. |
| Plugin Management | This document lists the plugins that are defined through pluginManagement. |
| Project License | This is a link to the definitions of project licenses. |
| Project Plugins | This document lists the build plugins and the report plugins used by this project. |
| Project Summary | This document lists other related information of this project |
| Project Team | This document provides information on the members of this project. These are the individuals who have contributed to the project in one form or another. |
| Source Repository | This is a link to the online source repository that can be viewed via a web browser. |