Storage: Difference between revisions
Jump to navigation
Jump to search
(add use cases for the separation of indexing from storage) |
|||
| Line 4: | Line 4: | ||
=== Full Text Indexing === | === Full Text Indexing === | ||
* separation of indexing from storage | * separation of indexing from storage | ||
** Firefox could use this to index visited web pages without having to store the contents of the pages themselves. | |||
** Thunderbird could use this to index email messages without having to store their contents in SQLite (ultimately it might make sense to store contents as well, but that's a larger, longer-term change). | |||
** Komodo could use this to index source code stored in files on disk. | |||
* built-in tokenization of Unicode text (i.e. without having to either compile in a large separate library or write custom functions); | * built-in tokenization of Unicode text (i.e. without having to either compile in a large separate library or write custom functions); | ||
* tokenization of marked up text (HTML, PDF, etc.). | * tokenization of marked up text (HTML, PDF, etc.). | ||
Revision as of 23:52, 11 March 2008
Storage is a SQLite database API. API documentation is available in the Mozilla Developer Center.
Proposed Future Development Priorities
Full Text Indexing
- separation of indexing from storage
- Firefox could use this to index visited web pages without having to store the contents of the pages themselves.
- Thunderbird could use this to index email messages without having to store their contents in SQLite (ultimately it might make sense to store contents as well, but that's a larger, longer-term change).
- Komodo could use this to index source code stored in files on disk.
- built-in tokenization of Unicode text (i.e. without having to either compile in a large separate library or write custom functions);
- tokenization of marked up text (HTML, PDF, etc.).