Changes between Version 10 and Version 11 of FSDesign

Timestamp:

2009-07-23T20:20:05Z (16 years ago)

Author:

Jakub Jermář

Comment:

—

FSDesign

@@ -42 +42 @@
 opened files, and in some special cases also VFS triplets (see below).
 
+=== Paths as Arguments ===
+
 If the argument is a file path, VFS uses the ''vfs_lookup_internal()'' function to
 translate the path into the so called lookup result represented by the ''vfs_lookup_res_t''
@@ -61 +63 @@
 node, for which there is the ''vfs_node_t'' type. Thus, a VFS node represents
 some file which is referenced by VFS. VFS nodes are the first class entities
-in the VFS server, because in most operations, a VFS node must be instantiated.
+in the VFS server, because for most operations it needs to have the VFS node.
 
 The VFS server calls the ''vfs_node_get()'' function in order to get a VFS node
@@ -91 +93 @@
 The example is simplified and does not show all the details (e.g. it omits all synchronization), but it shows the main idea. Note the trailing ''vfs_node_put()'' function which drops a reference to a VFS node. If the last reference is dropped from a node, ''vfs_node_put()'' removes it from the hash table and cleans it up.
 
+=== Handles as Arguments ===