From 9bdc18602ac9db7c81907d21845a5666af362afd Mon Sep 17 00:00:00 2001 From: Stefano Ceccherini Date: Tue, 10 Sep 2002 13:08:53 +0000 Subject: [PATCH] BMemoryIO use cases git-svn-id: file:///srv/svn/repos/haiku/trunk/current@1007 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- .../support/usecases/BMemoryIOUseCases.html | 107 ++++++++++++++++++ 1 file changed, 107 insertions(+) create mode 100644 docs/develop/support/usecases/BMemoryIOUseCases.html diff --git a/docs/develop/support/usecases/BMemoryIOUseCases.html b/docs/develop/support/usecases/BMemoryIOUseCases.html new file mode 100644 index 0000000000..acb6ca9113 --- /dev/null +++ b/docs/develop/support/usecases/BMemoryIOUseCases.html @@ -0,0 +1,107 @@ + + + +BMemoryIO Use Cases and Implementation Details + + + + + + +

BMemoryIO Use Cases and Implementation Details:

+ +

This document describes the BMemoryIO interface and some basics of how it is implemented. +The document has the following sections:

+ +
    +
  1. BMemoryIO Interface
    2. +
  2. BMemoryIO Use Cases
    3. +
  3. BMemoryIO Implementation
    4. +
+ +

BMemoryIO Interface:

+ +

The BMemoryIO class represent a buffer of dynamically allocated memory. You assign the +buffer to a BMemoryIO object on construction. The best source of information for the BMemoryIO interface +can be found +here in the Be Book. +

+ +

BMemoryIO Use Cases:

+ +

The following use cases cover the BMemoryIO functionality:

+ +
    + +

  1. Construction 1: A BMemoryIO can be created by specifying a void pointer +and a ssize_t option. These options are used to determine the buffer to assign to the BMemoryIO object and its +size. No check is done to determine if the buffer is valid or if it contains at least the number of byte specified.

    2. + +

  2. Construction 2: As the one above, but the buffer is specified with a const void pointer. +The BMemoryIO object becomes read only, and every subsequent Write(), WriteAt() and SetSize() calls will +return B_NOT_ALLOWED.

    3. + +

  3. Destruction: The BMemoryIO destructor does nothing. It's up to the caller the responsibility +to free the buffer assigned on construction.

    4. + +

  4. Reading 1: When ReadAt() is called, the BMemoryIO returns the number of bytes read from the specified +position. ReadAt() takes three arguments: the position where to begin the read operation, the buffer where to put the read data, +and the number of bytes to read. This function does not read outside of the buffer. +If the specified position is invalid (i.e. outside bounds) this function returns 0. If the read operation +begins at a valid position, but the sum of position and bytes to read is bigger than the max size (specified on construction), BMemoryIO +returns just the available data.

    5. + +

  5. Reading 2. BMemoryIO inherits the Read() function from BPositionIO. This function read the specified amount +of data from the current position, and put it into the specified buffer, then it moves the I/O index forward of the number of read bytes. +This function behaves like the above.

    6. + +

  6. Writing 1: When WriteAt() is called, BMemoryIO returns the number of bytes written to the specified position. +WriteAt() takes three arguments: the position where to begin the write operation, the buffer from which to read the data to write, and the +number of bytes to write. If the BMemoryIO object was constructed with the const constructor, this function returns B_NOT_ALLOWED. +This function does not write outside of the buffer bounds. If the specified position is invalid (i.e. outside bounds) this function returns 0. If the write operation begins at a valid position, but the sum of position and bytes to write is bigger than the max size (specified on construction), BMemoryIO +returns just the amount of data which can be written. +If the BMemoryIO object has been shrunk (see the Size Change case), and the write operation is outside the current bounds (but inside the +bounds specified on construction) this function re-enlarge it to accomodate the data.

    7. + +

  7. Writing 2. BMemoryIO inherits the Write() function from BPositionIO. This function write the specified amount +of data to the current position of the BMemoryIO object, reading from the specified buffer, then it moves the I/O index forward +of the number of read bytes. +This function behaves like the above.

    8. + +

  8. Size Changes: The SetSize() member function enlarges or shrink the amount of data which can be read/write. +If the BMemoryIO object was constructed with the const constructor, this function always returns B_NOT_ALLOWED. +Any SetSize call with a size parameter bigger than the size specified on construction will fail and return B_ERROR. Shrinking the buffer +is always possible, and the function returns B_OK. Negative values are not allowed, and the function returns B_ERROR. +

    9. + +

  9. Seeking. Seek() sets the position in the data buffer where the Read() and Write() functions (inherited from +BPositionIO) begin reading and writing. How the position argument is understood depends on the mode flag. There are three possible modes: +

      +

    • + SEEK_SET. The position passed is an offset from the beginning of allocated memory; in other + words, the current position is set to position. For this mode, position should be a positive + value, but the BMemoryIO object doesn't do any checking, so it is possible to seek to a negative position + (but any consequent Read() or Write() calls will fail). +

      • +

    • + SEEK_CUR. The position argument is an offset from the current position; the value of the + argument is added to the current position.

      • +

    • + SEEK_END. The position argument is an offset from the end of the buffer for a BMemoryIO + object. Positive values seek beyond the end of the buffer or data; negative + values seek backwards into the data.

      • +
    +Seek() Always return the new position. +

    10. + +

  10. Position: The Position() call always return the current position.

    11. + +
+ +

BMemoryIO Implementation:

+ +

The implementation of the BMessageFilter is simple. It consist in implementing memory read/write on a buffer +with an index.

+ + + \ No newline at end of file