Offer an (optionnal) cache mechanism

[arthurlutz]

I don't know if this should be in pagekite (or in a pagekite architecture) but it would be nice to switch to a cached version of the site when it is offline.

Again, making it optionnal.

Added cool things :

• have a banner stating that it is the offline version
• should information about when this cached version was made
• disable interactions (safeguards for POST for example would be a start)

[pagekite]

I agree this would be great. It's rather tricky though, because doing this properly requires adding a complete HTTP parser inside pagekite.py and a mechanism for rerouting requests to an external cache - which would then send the request back to pagekite for forwarding to the actual back-end. This would be really useful though, because it wouldn't just increase availability, it would improve performance and lighten the load on the user's webserver. With this, pagekite enabled sites would actually be able to handle slashdottings and such fun events.

This is on our long-term TODO, but we're focusing on more low hanging fruit for now. :-)

[BjarniRunar]

Having thought about this, this is no longer on our TODO list. There are other caching proxies out there, combining them with PageKite should be the way to do this. Thanks for filing!

[BjarniRunar]

Actually, going to reopen this and mark as "Would Accept Pull Request" - if someone wants to do the work, we wouldn't reject it! The best way to do this is still to use an external cache, but as mentioned above, some hooks in PageKite itself might be necessary for that to perform and function well.