Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add API point to add an event listener #89

Open
infeo opened this issue Aug 20, 2020 · 0 comments
Open

Add API point to add an event listener #89

infeo opened this issue Aug 20, 2020 · 0 comments

Comments

@infeo
Copy link
Member

infeo commented Aug 20, 2020

Summary

Add an API to hand over/add an event listener to cryptofs. The event listener is bidirectional, i.e. does not only report but also returns a value. It is our decision to which events the listener is triggered (e.g. failed reading of a file, not existing directory, etc)

Problem Description

In cryptofs there are cases where it would be good to inform the caller about certain events/findings (e.g. files not belonging to the vault structure, invalid dir directories). Currently, only an error is thrown and the operation aborted or the event is logged, but otherwise ignored. From the caller perspective this is not the most desireable case, because with this you might miss (for you) important findings.

Solution

Expose in the API a method to add an eventlistener and then notify the listener on predefined events. The predefined events should be documented somewhere. For example there could be an extended method for filesystem creation, where one can hand over the event listener.

Alternatives

Collecting all occuring, not critical exceptions and then hand them over (in some way) to the caller. But this would require again some side channel.

@infeo infeo changed the title Add method to add an Eventlistener for other events then warnings Add API point to add an event listener. Jan 10, 2025
@infeo infeo changed the title Add API point to add an event listener. Add API point to add an event listener Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant