web commit by flaviocruz

1 files changed, 4 insertions, 6 deletions

diff --git a/community/flavioc.mdwn b/community/flavioc.mdwn
index a0c0d036..5f83cd62 100644
--- a/community/flavioc.mdwn
+++ b/community/flavioc.mdwn
@@ -26,7 +26,6 @@ Creating an extensible translator library in lisp using the mig generated stubs.
 
 - The library for writing translators is mostly written.
 - This library is intended to implement virtual filesystems. Examples are: translators were data is located in a local file (like zipfs, tarfs, rarfs, ...), single file translators (that do content filtering, output of a command, etc), network based filesystems (ftpfs, httpfs, ...)
-- Right now, what's missing is: support for symlinks, file execution, and setting other translators on our node tree.
 - It's possible to specialize the basic translator library and implement new translator classes. This is done using CLOS.
 - There is a tree-translator class that makes the managing of a node tree very easy, doing all the work for us, through a simple directory API and implementing the directory callbacks for us.
 - There is a simple example (something like zipfs) translator that can expose the directories and file contents of a ZIP file.
@@ -49,12 +48,11 @@ Creating an extensible translator library in lisp using the mig generated stubs.
 ### What needs to be done
 
 - Using continuations for IO blocking operations. This can be done using cl-cont.
-- Callbacks:
-  - file_lock, file_lock_stat (still not sure if they are really needed)
-  - file_reparent
-- Bind the client RPC calls.
+- Create an example proxy translator.
+- Fix file_exec, fsys_getroot (block happens in trivfs based translators, when they do RPC's to me when I call fsys_getroot to them) and fetch_root (for passive translators).
 - Use the socket stubs?
-
+- Documentation
+- More testing
 
 ### Notes