summaryrefslogtreecommitdiff
path: root/community/gsoc
diff options
context:
space:
mode:
authorGNU Hurd wiki engine <web-hurd@gnu.org>2008-03-11 21:04:33 +0000
committerGNU Hurd wiki engine <web-hurd@gnu.org>2008-03-11 21:04:33 +0000
commit1cc10ff265ce6a3f7a6a9d23792b02dd03083c13 (patch)
tree1e1d25e8d86fa5d9e46daa10409977a3957bc517 /community/gsoc
parenta43fb3ea81db9814baecb6e7deb5e1a12cc60062 (diff)
web commit by hammy: Removed ``translator stacking mechanism''. Already assigned to Carl Fredrik Hammar.
Diffstat (limited to 'community/gsoc')
-rw-r--r--community/gsoc/project_ideas.mdwn41
1 files changed, 0 insertions, 41 deletions
diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn
index 661f8839..c6a721d5 100644
--- a/community/gsoc/project_ideas.mdwn
+++ b/community/gsoc/project_ideas.mdwn
@@ -8,47 +8,6 @@ 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]]."]]"""]]
-* translator stacking mechanism
-
-One of the major strengths of the Hurd design is that not only it uses a
-modular (multiserver) architecture internally, but also encourages a similar
-modular architecture at application level. Complex applications can be created
-intuitively from simple components by combining them through translator
-stacking -- similar to traditional UNIX pipes, but much more suitable for
-complex interaction and structured data.
-
-The downside is that communication between the components with filesystem- or
-other RPC interfaces imposes a relatively high overhead: Not only are the
-actual IPC operations relatively slow in Mach, but also communication is
-generally more complicated because of the constraints of an RPC interface.
-
-In some cases, like network stacks for example, the overhead might prove a
-serious problem; a mechanism that allows cutting down on it by more or less
-transparently, taking a shortcut in certain situations to avoid actual RPC, is
-highly desirable.
-
-The work on [[libchannel]] as a special-purpose translator stacking mechanism
-as last year's GSoC project yielded some very interesting ideas for a more
-generic translator stacking framework.
-
-(links)
-
-The task here is to follow up on the previous work, creating a framework based
-on these ideas, and implementing or porting some translators based on this
-framework to prove it's applicability in practice. It is up to the student to
-decide whether it's better to start with the previous libchannel code, turning
-it into something more generic; or starting from scratch, using libchannel (and
-libstore) only for reference.
-
-This task is pretty involved. The architecture of the stacking framework has
-been discussed before; but the student needs to design the various actual
-interfaces for the framework, and implement all of them.
-
-Last years student might be able to get this done before GSoC starts. If
-you're interested in this project send a mail to
-[Carl Fredrik Hammar](mailto:hammy.lite@gmail.com) to make sure he has not
-already gotten started with it.
-
* sound support
The Hurd presently has no sound support. Fixing this requires two steps: One is