Now in a library project, my students’ notes are loaded in the form of paging ajax, but now I have encountered a problem in synchronizing cache updates. I would like to ask all netizens for advice.
For example, when a student deletes an article, I need to update the cache in the paging at the same time. Because it is loaded in the form of ajax, there is a problem with the interaction between the front and back ends.
It seems that it is not clearly stated, that is, when a user deletes a note, how do I know which page the note belongs to? I have thought of some solutions myself, but it will take some time to change a lot of front-end code. Can any netizens give some suggestions?
p.s: The business is not that simple. For example, when a user browses a note alone, there is no statistical pagination information.
The problem has been solved, I recommend the previous article on quora -> https://www.quora.com/Why-doe...
Actually, my questions are more about the details of the business, and have little to do with the above article. I recommend friends who do caching to read it.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
You can check this out: http://bbs.csdn.net/topics/39...
Questioner, you have asked this question before, but I don’t know what the final solution is. If you use an external index, then when you delete a note, you don’t need to care about which page. You can just delete the note and delete the relationship at the same time. There is no need to create a cache for relationships.
The problem has been solved, I recommend the previous article on quora -> https://www.quora.com/Why-doe...
Actually, my questions are more about the details of the business and have little to do with the above article. I recommend friends who do caching to read it.
Don’t you know which page it belongs to when making an ajax request on the front end?