jerboaburrow / busser Goto Github PK

• add age, last modified, cache-control

https://docs.rs/openssl/latest/openssl/version/index.html

• stats for top pages (.html's)
• stats for top content
• top 3 now to n

• run it as non blocking

Trait to handle disk changes

probably best not to use meta as this may have unforeseen side effects, the comment will be a comment

https://stackoverflow.com/questions/77802837/is-it-a-bad-idea-to-use-the-meta-tag-in-html-to-specify-custom-metadata-for-retr

• list of regexes to ignore
• still collect the stats, just don't report in digest

e.g. ignore favicon.ico, or .svg (both regexes)

move

• save hitstats
• archive

add a stats file

• trace time series of hits to given paths in stats config
• give paths as vector

• Observe content
• in the into_response check if the file is stale? (this adds ~ 1 milli) will need to benchmark, follow the pages cache? forced reloads?
• config to make the server webpage static (no updates within one program run)

• option in config
• task to perform zip compression https://github.com/zip-rs/zip2

• Generate a dynamic site map
• support image and video

• config option to ignore, e.g. . files etc

• use hashes of address plus path
• only throttle repeated
• benchmark

• is image
• is video
• is text

• hash formed of uri's (structure)
• hash formed of uri's and their associated Content hashes (after a load)

Implement a File trait for loading and saving to files

• optionally suppress build time in sitemap

• resolve bug

• option in stats config to compress when clearing

• authenticate POSTS
• e.g. POST to get stats digest message etc...

• post functions and state, and a time, to a scheduler
• scheduler loops and executes when the next job is run-able
• split stats thread into multiple jobs

• build without loading
• separate load_content method

• report at fixed point rather than fixed duration
• optional day, and hour/min

Enable swapping out the server (when the sitemap structure is updated)

• Observe the structure hash (i.e.. uri's)
• when structure has is stale, prepare new router, graceful shutdown, swap
• configure refresh rate in a watcher thread

Or maybe we can append routes to a served Server?

• stats from and to
• from and or to can be neglected for open ranges

• https://github.com/rust-lang/git2-rs/tree/master

Content handles uri, body, disk path and cache (is static)

Page and Resource differentiate in how they are served (plus found via file extensions)

• compile stats
• discord integration

• move then compress them

• dynamic content options (compile options?)
• check with hashes

• Digests
• Hit processing
• File i/o