CBFS Connect 2020 Python Edition

Questions / Feedback?

on_delete_reparse_point Event

Fires when the OS wants to delete a reparse point from a file or directory.

Syntax

class CBFSDeleteReparsePointEventParams(object):
  @property
  def file_name() -> str: ...
  @property
  def reparse_buffer() -> c_void_p: ...
  @property
  def reparse_buffer_length() -> int: ...
  @property
  def handle_info() -> int: ...
  @property
  def file_context() -> int: ...
  @file_context.setter
  def file_context(value) -> None: ...
  @property
  def handle_context() -> int: ...
  @handle_context.setter
  def handle_context(value) -> None: ...
  @property
  def result_code() -> int: ...
  @result_code.setter
  def result_code(value) -> None: ...

# In class CBFS:
@property
def on_delete_reparse_point() -> Callable[[CBFSDeleteReparsePointEventParams], None]: ...
@on_delete_reparse_point.setter
def on_delete_reparse_point(event_hook: Callable[[CBFSDeleteReparsePointEventParams], None]) -> None: ...

Remarks

This event fires when the OS wants to delete a reparse point from the file or directory specified by FileName.

This event only needs to be handled if the use_reparse_points property is enabled. To handle this event properly, applications must delete the reparse point data (and tag) stored previously for the specified file or directory. Any other actions taken in an earlier on_set_reparse_point event should also be reversed appropriately. Note that the file or directory itself should not be deleted.

Please refer to the Reparse Points topic for more information.

The existing reparse point data is provided in this event as a convenience for use-cases that wish to utilize it.

The HandleInfo parameter carries a handle to an object with information about the file handle. While within the event handler, it can be used to call any of the following methods: get_handle_creator_process_id, get_handle_creator_process_name, get_handle_creator_thread_id, or get_handle_creator_token.

The FileContext and HandleContext parameters are placeholders for application-defined data associated with the file and specific handle, respectively. Please refer to the Contexts topic for more information.

Please refer to the Buffer Parameters topic for more information on how to work with memory buffer event parameters.

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.

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