CBFS Vault 2020 Python Edition

Questions / Feedback?

on_vault_set_size Event

Fires to resize a callback mode vault.


class CBVaultVaultSetSizeEventParams(object):
  def vault_handle() -> int: ...
  def new_size() -> int: ...
  def result_code() -> int: ...
  def result_code(value) -> None: ...

# In class CBVault:
def on_vault_set_size() -> Callable[[CBVaultVaultSetSizeEventParams], None]: ...
def on_vault_set_size(event_hook: Callable[[CBVaultVaultSetSizeEventParams], None]) -> None: ...


This event fires when the class needs to resize the callback mode vault specified by VaultHandle.

This event only needs to be handled if the callback_mode property is enabled; please refer to the Callback Mode topic for more information. To handle this event properly, applications must grow or shrink the vault specified by VaultHandle in order to reach the specified NewSize. When growing a vault, applications do not need to sanitize newly-allocated space.

The VaultHandle parameter contains an application-defined handle to an open callback mode vault, as returned by the application in an earlier on_vault_open event.

The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource isn't available, security checks failed, etc.), set it to a non-zero value to report an appropriate error. Please refer to the Error Reporting and Handling topic for more information.

Note: An application should not attempt to call class's methods from handlers of this event. Doing this is guaranteed to cause a deadlock.

Note: when a storage is opened concurrently in read-only mode by several applications using CBDrive or CBMemDrive class, the event will fire only in the first application. To prevent such a situation, always open a vault in read-write mode.

Copyright (c) 2021 Callback Technologies, Inc. - All rights reserved.
CBFS Vault 2020 Python Edition - Version 20.0 [Build 7982]