diff options
| author | Thomas Schwinge <thomas@schwinge.name> | 2010-03-28 21:48:46 +0200 |
|---|---|---|
| committer | Thomas Schwinge <thomas@schwinge.name> | 2010-03-28 21:48:46 +0200 |
| commit | 4b35fc7bdd7ab723cb3db8e9122ed08d996f33b4 (patch) | |
| tree | e4bb2ffadd136ab05b8abc3c0fa9f305f8c360fe /community/gsoc/project_ideas/namespace-based_translator_selection.mdwn | |
| parent | 34794c7002f679ab9c2d076284ff58288224c47d (diff) | |
| parent | 96611f76b833159bafeab3443229dfa690178d92 (diff) | |
Merge commit '96611f76b833159bafeab3443229dfa690178d92' into master-news_next
Conflicts:
news/2010-03-31.mdwn
Diffstat (limited to 'community/gsoc/project_ideas/namespace-based_translator_selection.mdwn')
| -rw-r--r-- | community/gsoc/project_ideas/namespace-based_translator_selection.mdwn | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/community/gsoc/project_ideas/namespace-based_translator_selection.mdwn b/community/gsoc/project_ideas/namespace-based_translator_selection.mdwn index d40d73ac..67e3fc28 100644 --- a/community/gsoc/project_ideas/namespace-based_translator_selection.mdwn +++ b/community/gsoc/project_ideas/namespace-based_translator_selection.mdwn @@ -8,7 +8,7 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] -[[!meta title="Namspace-based Translator Selection"]] +[[!meta title="Namespace-based Translator Selection"]] The main idea behind the Hurd is to make (almost) all system functionality user-modifiable ([[extensible_system|extensibility]]). This includes a @@ -26,7 +26,7 @@ file, and presents a virtual file with the uncompressed contents. Or the other way around. Or a translator that presents an [[XML_file_as_a_directory_tree|hurd/translator/xmlfs]]. Or an mbox as a set of individual files for each mail ([[hurd/translator/mboxfs]]); or ever further -breaking it down into headers, body, attachements... +breaking it down into headers, body, attachments... This gets even more powerful when translators are used as building blocks for larger applications: A mail reader for example doesn't need backends for @@ -40,7 +40,7 @@ There are a few problems with the way translators are set, though. For one, once a translator is set on a node, you always see the translated content. If you need the untranslated contents again, to do a backup for example, you first need to remove the translator again. Also, having to set a translator -explicitely before accessing the contents is pretty cumbersome, making this +explicitly before accessing the contents is pretty cumbersome, making this feature almost useless. A possible solution is implementing a mechanism for selecting translators @@ -61,7 +61,7 @@ place of the original ones. In the long run it's probably desirable to have the mechanism implemented in the standard name lookup mechanism, so it will be available globally, and avoid -the overhead of a proxy; but for the beginnig the proxy solution is much more +the overhead of a proxy; but for the beginning the proxy solution is much more flexible. The goal of this project is implementing a prototype proxy; perhaps also a |