From 48beeede9737a53f277b570045c1d41cbcdabfb4 Mon Sep 17 00:00:00 2001 From: pictuga Date: Fri, 20 Mar 2020 11:27:05 +0100 Subject: [PATCH] README: update cache part --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 422f9de..fb3e456 100644 --- a/README.md +++ b/README.md @@ -222,12 +222,12 @@ output = morss.Format(rss, options) # formats final feed ## Cache information -morss uses a small cache directory to make the loading faster. Given the way -it's designed, the cache doesn't need to be purged each while and then, unless -you stop following a big amount of feeds. Only in the case of mass un-subscribing, -you might want to delete the cache files corresponding to the bygone feeds. If -morss is running as a server, the cache folder is at `MORSS_DIRECTORY/cache/`, -and in `$HOME/.cache/morss` otherwise. +morss uses caching to make loading faster. There are 2 possible cache backends +(visible in `morss/crawler.py`): + +- `SQLiteCache`: sqlite3 cache. Default file location is in-memory (i.e. it will +be cleared every time the program is run +- `MySQLCacheHandler`: /!\ Does NOT support multi-threading ## Configuration ### Length limitation