Optimisation for when user presses back button

[gedw99]

Hey @1cg

thanks for this amazing project . It’s so simple and that’s a good thing .

i am exploring how to get the back button scenarios working so it’s instant and simple .

Client side page caching and when to invalidate when the users goes back is an interesting area.

The previous page is cached and so the data used to render may be old data.

How to know ? You need to track in the server what data they used and if it’s changed. There are many options to do this and they are quite complex and I wanted to talk about one way ..

CQRS is a pattern on servers to y out write data from read data . The age old problem is tracking it all the way up to web pages. It’s Ben worse with shared reusable components.

so there are static page generators and if we gen pages there and know exactly what’s data every pages uses we can know for sure when a page is stake,and easily tell the browser when the user goes back.

The mapping of data ( both in your db and rest third party system you called ) is another matter that is too complex to talk about but the solution is to use CDC.

So what about the idea of tracking if the previous page is stale. How can we do it with htmx ?

I am Building up an example of the CQRS and CDC backend to make public but don’t know how htmx manages previous cached page invalidation .

So please offer suggestions if you might know

[gedw99]

If anyone wants an e ample of the CQRS and CDC backend let me know. It’s golang