Skip to content

Lifecycle hooks #19

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.

Sign up for GitHub

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

Draft
zshipko wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Lifecycle hooks #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions EIP-010-lifecycle-hooks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Lifecycle hooks

## Purpose

To provide hosts more insight into plugin resource usage.

## Solution

Provide a set of callbacks that are executed at specific points in the plugin's lifecycle. Where these callbacks are stored
and how they're executed is still up for discussion.

## Considerations

Some of these hooks could be implemented at the kernel-level - this would likely require hosts that use the kernel to implement
additional host functions to thread the configured host hook through. Kernel-level hooks could be used to track things like
allocations in Extism memory and errors.

Other hooks, specifically around when plugin execution starts and stops, would have to be implemented in each runtime because the
kernel doesn't have that information.

There may also be more runtime-specific ways of implementing these hooks - for example, Wasmtime already provides a memory limiter
that could be used to implement hooks around memory use.