-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Article tags and cache invalidation #356
Comments
Perhaps tags should be added to articleContents, and not articles. That way, we get versioning of tags as well. |
We probably don't want to do this for performance reasons. |
Adding them to article contents instead doesn't really fix the problem, as the rendered article will still be cached. |
I meant that every time we do a change to the tags, we make a new articlecontent with a new set of tags based off the old one. |
I like this suggestion. It is compatible with #357 |
Incidentally, this also allows tags to be added to the english version of a compendium and not the norwegian |
That's not nessecesarily a good thing. If a person searches for |
Yes, but in the scenario you describe, the user is searching for a tag that nobody has added yet, right? Then that is the reason why there are no search results. Anyway, the search engine can be designed to broaden the search (full text search in the backend?) in case the quick front end search yields no results. That should cover most scenarios. |
I described a scenario where |
We currently cache the entire rendered article view per user.
Until now, this has been fine, since the cache is not re-used once a new articleContent is created.
But with tags, this caching introduces a problem.
We already cache the html output of each ArticleContent, so I guess the easiest fix might be to stop caching of the rendered article.html
The text was updated successfully, but these errors were encountered: