12 <concept xml:lang="en" id="GUID-AF65EC50-0922-57DD-809B-DB8970C8E4C6"><title>File server session</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>All files are handled by the file server, using either its local file system, or an installed file system. The server manages i/o activity, and contention, sharing and locking. </p> <p>Client programs access the file server through a client API defined in <filepath>f32file.h</filepath>. This API includes all classes and functions needed for file system, device, directory and file access, and associated utilities. </p> <p>All access from client to server is through a file server session, an instance of the <codeph>RFs</codeph> class. After a client has connected an <codeph>RFs</codeph> to the file server, it can perform any file-related operation. An <codeph>RFs</codeph> is associated with a single current path: when a connection to the file server is made the session path is automatically set to the private directory of the connecting process. </p> <p>After operations have been completed, file server-related clean-up should be carried out using <codeph>Close()</codeph> defined in the <codeph>RHandleBase</codeph> class. Note that for the majority of functions, when a file or directory name is passed as an argument to the function, if no drive letter or directory is specified, the missing path component will be taken from the <keyword>session path.</keyword> </p> <p><b>Component-based design </b> </p> <p>Only a single path is supported, and the path includes the drive. Each component must have its own <codeph>RFs</codeph> for its file access purposes. This gives each component all the flexibility it needs to maintain its own current path and other settings related to an <codeph>RFs</codeph>. There is no limit on the number of <codeph>RFs</codeph> handles available to a single thread. </p> <p>This is unlike DOS, which effectively maintains 26 current paths, one for each drive. DOS also maintains a current drive, and the effective current path is therefore the current path on the current drive. </p> </conbody></concept>

    12 <concept id="GUID-AF65EC50-0922-57DD-809B-DB8970C8E4C6" xml:lang="en"><title>File

    13 server session</title><shortdesc>This topic describes the file server session concept.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>

    14 <p>All files are handled by the file server, using either its local file system,

    15 or an installed file system. The server manages i/o activity, and contention,

    16 sharing and locking. </p>

    17 <p>Client programs access the file server through a client API defined in <filepath>f32file.h</filepath>.

    18 This API includes all classes and functions needed for file system, device,

    19 directory and file access, and associated utilities. </p>

    20 <p>All access from client to server is through a file server session, an instance

    21 of the <codeph>RFs</codeph> class. After a client has connected an <codeph>RFs</codeph> to

    22 the file server, it can perform any file-related operation. An <codeph>RFs</codeph> is

    23 associated with a single current path: when a connection to the file server

    24 is made the session path is automatically set to the private directory of

    25 the connecting process. </p>

    26 <p>After operations have been completed, file server-related clean-up should

    27 be carried out using <codeph>Close()</codeph> defined in the <codeph>RHandleBase</codeph> class.

    28 Note that for the majority of functions, when a file or directory name is

    29 passed as an argument to the function, if no drive letter or directory is

    30 specified, the missing path component will be taken from the <keyword>session

    31 path.</keyword> </p>

    32 

    33 

    34 <p><b>Component-based design </b> </p>

    35 <p>Only a single path is supported, and the path includes the drive. Each

    36 component must have its own <codeph>RFs</codeph> for its file access purposes.

    37 This gives each component all the flexibility it needs to maintain its own

    38 current path and other settings related to an <codeph>RFs</codeph>. There

    39 is no limit on the number of <codeph>RFs</codeph> handles available to a single

    40 thread. </p>

    41 <p>This is unlike DOS, which effectively maintains 26 current paths, one for

    42 each drive. DOS also maintains a current drive, and the effective current

    43 path is therefore the current path on the current drive. </p>

    44 </conbody></concept>