refactor: remove redundant mtime check from HTTP handlers#77
Merged
jfernandez merged 1 commit intomainfrom Mar 26, 2026
Merged
Conversation
HTTP handlers now serve pre-rendered HTML from memory without re-checking the file on disk. The file watcher is the sole mechanism for keeping content fresh, which aligns with the pre-rendered in-memory design.
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows up on #76. HTTP handlers now serve from memory without re-reading from disk on every request. The file watcher is the sole mechanism for keeping content fresh.
refresh_file(mtime-checking variant), renameforce_refresh_filetorefresh_filerefresh_filecalls fromserve_html_rootandserve_fileThis aligns with the pre-rendered in-memory design: startup renders all files, the watcher updates on change, HTTP just serves what's in memory.