Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/designs/PDOM"
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== PDOM & Indexing === | === PDOM & Indexing === | ||
This section describes the design for the new indexing architecture in CDT 3.1. It essentially revolves around a new database for indexing information, the PDOM, which stores binding and name elements as they would appear in the DOM. Thus the term Persisted DOM, PDOM. Since DOM information is being stored in the index, we can now use it for more things as well as use it to speed up indexing. | This section describes the design for the new indexing architecture in CDT 3.1. It essentially revolves around a new database for indexing information, the PDOM, which stores binding and name elements as they would appear in the DOM. Thus the term Persisted DOM, PDOM. Since DOM information is being stored in the index, we can now use it for more things as well as use it to speed up indexing. | ||
| − | * [[History]] | + | * [[CDT/designs/PDOM/History | History]] |
| − | * [[Overview]] | + | * [[CDT/designs/PDOM/Overview | Overview]] |
| + | * [[CDT/designs/PDOM/Lifecycle | PDOM Lifecycle]] | ||
Latest revision as of 17:49, 28 March 2006
PDOM & Indexing
This section describes the design for the new indexing architecture in CDT 3.1. It essentially revolves around a new database for indexing information, the PDOM, which stores binding and name elements as they would appear in the DOM. Thus the term Persisted DOM, PDOM. Since DOM information is being stored in the index, we can now use it for more things as well as use it to speed up indexing.