Please provide some justification for this. Plugins must be shutdown when exiting Sigil otherwise their output is lost (by design) and if Sigil is crashing, that should not happen.
What potential use is this? How would this help the majority of Sigil users? As you pointed out, the implementation of a session id is easy to do. The real question is why? Please provide complete examples of how this helps.
Quote:
Originally Posted by mrprobert
Feature Request: Session ID for Plugin Cache Invalidation
I've written up a feature request for adding a Session ID to Sigil's plugin API. This would enable plugins to reliably cache expensive computations by detecting when Sigil has restarted.
Full proposal with implementation details:
https://gist.github.com/mrprobert/77...d5c20a23af8638
TL;DR:
- Problem: Plugins can't tell if Sigil restarted between invocations
- Solution: Add a simple session identifier (timestamp_pid format) |