202
1 1
U S E R - L E V E L A P I
The salient point of this example is not the specific case of creating key-
word attributes but rather to show the ease with which programs can in-
corporate these features. With only a few lines of code a program can add
attributes and indices, which then gives the ability to issue queries based on
those attributes.
11.4
Summary
The two user-level BeOS APIs expose the features supported by the vnode
layer of the BeOS and implemented by BFS. The BeOS supports the tradi-
tional POSIX file I/O API (with some extensions) and a fully object-oriented
C++ API. The C++ API offers access to features such as live queries and node
monitoring that cannot be accessed from the traditional C API. The func-
tions accessible only from C are the index functions to iterate over, create,
and delete indices.
The design of the C++ API provoked a conflict between those advocating
the Macintosh-style approach to dealing with files and those advocating the
POSIX style. The compromise solution codified in the BeOS class hierarchy
for file I/O is acceptable and works, even if a few parts of the design seem less
than ideal.
Practical File System Design:The Be File System
, Dominic Giampaolo
page 202
Summary :
202 1 1 U S E R - L E V E L A P I The salient point of this example is not the specific case of creating key- word attributes but rather to show the ease with which programs can in- corporate these features.
Tags :
api,beos,file,features,those,attributes,system,indices,few,202,node,design,only