Skip to content

Request-based Logging #127

@i2h3

Description

@i2h3

This is drafting an idea to further improve on in logging to have a clearer picture on what is happened during later problem analysis.

  • Every interaction with the file provider extension is based on a call from the framework to our implementation. The NSFileProviderReplicatedExtension documentation lists the most important ones.
  • The whole environment is highly concurrent. Multiple and different file system operations and enumerations can occur simultaneously. There might be multiple processes for the same file provider domain handling multiple item creation, modification or deletion requests while also enumerating some folder content. This still mixes up a lot of unrelated messages in the log.
  • The idea is to have a request object which is set up in the entry points to every call to our extension and closed afterwards to cohesively track what is happening in scope of it. It needs to be passed down the whole call stack, obviously.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions