diff options
| -rw-r--r-- | Hurd/TranslatorWishList.mdwn | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/Hurd/TranslatorWishList.mdwn b/Hurd/TranslatorWishList.mdwn index 3ba74bba..f00673ad 100644 --- a/Hurd/TranslatorWishList.mdwn +++ b/Hurd/TranslatorWishList.mdwn @@ -64,7 +64,15 @@ Here's an [idea](http://www.circlemud.org/~jelson/software/fusd/docs/node13.html * This may sound strange, but device file APIs have at least three advantages over a typical library API. First, it becomes much more language independent--any language that can make system calls can access the factorization library. Second, the factorization code is running in a different address space; if it crashes, it won't crash or corrupt the caller. Third, and most interestingly, it is possible to use `select(2)` to wait for the factorization to complete. `select(2)` would make it easy for a client to factor a large number while remaining responsive to other events that might happen in the meantime. In other words, FUSD allows normal user-space libraries to integrate seamlessly with UNIX's existing, POSIX-standard event notification interface: `select(2)`." --- [[Main/GregBuchholz]] - updated 08 Sep 2003 +## <a name="Mail"> Mail </a> + +Am I off my rocker, or does an IMAP/POP translator sound like a good idea? It would make your remote mail servers look like local ones. Or what about a translator that makes a mbox format mail spool look like a directory. Can anyone think of a good use for an SMTP translator? + +## <a name="UUEncode"> </a> UUEncode + +How about a UUEncode translator for those places you can only store ASCII. Combine this with a NNTP translator and store your data in someone's Usenet archive. Or since, (as far as I know), there are no size limitations on file names in the Hurd, why not have a translator whose underlying store is a file name. (Now ls becomes cat). + +-- [[Main/GregBuchholz]] - updated 08 Oct 2003 Minor formatting updates. |