IBlobManagementOptions class
Contents
[
Hide
]IBlobManagementOptions class
A Binary Large Object (BLOB) is a binary data stored as a single entity - i.e. BLOB can be an
audio, video or presentation itself. A number of techniques are used to optimize memory consumption
while working with BLOBs - which was already stored in the presentation or be added later programmatically.
Using IBlobManagementOptions
you can change a different behavior aspects regarding BLOBs
handling for the IPresentation
instance lifetime.
The IBlobManagementOptions type exposes the following members:
Properties
Property | Description |
---|---|
presentation_locking_behavior | This property defines if an instance of the Presentation class can be an owner of the source - file or stream during the instance lifetime. If the instance is an owner, it locks the source. This helps to improve memory consumption and performance while working with BLOBs, but the source (stream or file) can’t be changed during Presentation’s instance lifetime. This is an example: |
is_temporary_files_allowed | This property defines if temporary files can be created while working with BLOBs, what greatly decreases the memory consumption but requires permissions to create files. All files will be deleted after work with the presentation will be finished. |
temp_files_root_path | The root path where temporary files will be created. System temorary directory will be used by default. Hosting process should have permissions to create files and folders there. |
max_blobs_bytes_in_memory | Defines the maximum total size (in bytes) that all BLOBs may occupy in memory. By default, all BLOBs are loaded into memory; only once this limit is reached are alternative mechanisms (such as temporary files) employed. Keeping BLOBs in memory maximizes performance but can lead to high memory usage. Use this property to tailor behavior to your environment or requirements. |
See Also
- class
IBlobManagementOptions
- class
IPresentation
- module
aspose.slides
- library
Aspose.Slides