How -to use sessions efficiently

diff -r 48780e181b38 -r 578be2adaf3e Symbian3/PDK/Source/GUID-F4BD69B6-008E-51DB-ABFF-1E17E10B053F.dita --- a/Symbian3/PDK/Source/GUID-F4BD69B6-008E-51DB-ABFF-1E17E10B053F.dita Tue Jul 20 12:00:49 2010 +0100 +++ b/Symbian3/PDK/Source/GUID-F4BD69B6-008E-51DB-ABFF-1E17E10B053F.dita Fri Aug 13 16:47:46 2010 +0100 @@ -1,39 +1,39 @@ - - - - - -How -to use sessions efficientlyThis topic describes how to use file server session effectively. -

For most purposes, it is not necessary for the user of the file server -to be aware that it is implemented in a client-server architecture. However, -for some purposes, you can make your programs much more efficient if you are -aware of the implications of client-server interaction.

Essentially, you gain efficiency by using as few as possible client-server -calls. The main technique for achieving this is to transfer more data with -each file server function call. Things to watch out for include:

Data transfer: use a -large buffer, and then read bytes from the buffer. The main data-transfer -clients of the file server all operate through the stream store and the relational -database. Buffering has been highly optimized for these two components. Therefore, -application programs using these components automatically gain the maximum -efficiency in data transfer, without needing any explicit optimization.
Reading directories

There -are functions to read a single directory entry at a time, but it is often -more useful to read multiple directory entries from the server and then to -scan through them client-side.
Large-scale copying, -moving and other file management operations

A single class, CFileMan, -provides high-level function for this, involving only a small number of client-server -calls.

The TParseBase hierarchy of classes, for analyzing file -names, operates without client-server interaction.

+ + + + + +How +to use sessions efficientlyThis topic describes how to use file server session effectively. +

For most purposes, it is not necessary for the user of the file server +to be aware that it is implemented in a client-server architecture. However, +for some purposes, you can make your programs much more efficient if you are +aware of the implications of client-server interaction.

Essentially, you gain efficiency by using as few as possible client-server +calls. The main technique for achieving this is to transfer more data with +each file server function call. Things to watch out for include:

Data transfer: use a +large buffer, and then read bytes from the buffer. The main data-transfer +clients of the file server all operate through the stream store and the relational +database. Buffering has been highly optimized for these two components. Therefore, +application programs using these components automatically gain the maximum +efficiency in data transfer, without needing any explicit optimization.
Reading directories

There +are functions to read a single directory entry at a time, but it is often +more useful to read multiple directory entries from the server and then to +scan through them client-side.
Large-scale copying, +moving and other file management operations

A single class, CFileMan, +provides high-level function for this, involving only a small number of client-server +calls.

The TParseBase hierarchy of classes, for analyzing file +names, operates without client-server interaction.

\ No newline at end of file