[ ] Currently the implementation uses bytevector procedures to read static files and create responses with their content. Probably Guile's sendfile (see File-System in the Guile manual) is a more performant way of serving static files.
[ ] Keyboard interrupt (C-c) are not yet handled in a way that cleanly shuts down the server.
[ ] The various modules use different module systems. They should only use one module system.
[ ] Use exception handling instead of asking whether a file exists and then continuing to read the file without exception handling.
Reason: There is a chance that a file could be deleted immediately after an existence check and before the rest of the logic that depends on the file existing is executed.
[ ] Test cases for ~absolute-path~:
[ ] argument with prefix ~../~
[ ] Test cases for ~absolute-path?~:
[ ] argument with prefix ~../~
[ ] Test cases for ~path-join~:
[ ] Accept ~../~ in paths for path-join, going up one level.
[ ] Accept ~./~~ in parts for path-join, staying at the same level.
[ ] Accept /./ in parts for path-join, staying at root level.
[ ] No need to check, whether a path has any special parts in it, because the file procedures of Guile do not interpret them in any special way as Bash would do anyway. Only need to make sure, that a path is a subpath of the static directory.
[ ] Think about different naming for path functions. Apparently "path" is understood as list of "things leading to directories" in a string in the GNU ecosystem. However, "file" seems still unfitting to use for simply everything. Perhaps there is a better name.
