3 ms·
I've been thinking along similar lines for my project and the issue i'm running into conceptually is tracking WHICH cache records to invalidate upon POST. Say a
by jonah 16y ago
I've been thinking along similar lines for my project and the issue i'm running into conceptually is tracking WHICH cache records to invalidate upon POST. Say an HTML list, an HTML detail page, and a full composite object all contain references to the particular item you updated. Single items - the detail page and object are fairly easy to know about, but what about a list view and a grid view that also contain that item. What are your thoughts?
- jacques_chester 16y agoMy thoughts were to borrow a page from wikis and make links between documents a part of the model. For actual documents (blog posts, comments etc) I'd place them on disk. Metadata, including links between pages, would be in the database. With Postgres triggers + NOTIFY you can cause invalidation based on INSERTs and UPDATEs.
- roel_v 16y agoA dependency graph between database tables and pages, no? How to define 'page' depends on the rest of the application, I guess in most frameworks it would be 'module' + 'action'.