579 karma · joined October 13, 2011
Add a HTTP header on resource responses that is 1:1 with the deployment. When this header changes on any response, treat any associated resources in the cache as needing an If-Modified checkin.
Then add that header to a non-cached dynamic page, like the user's home page. When the browser checks this page and sees a deployment change, it'll know to check the static assets.
As billing account owner, my account was suspended. That meant I could no longer receive emails, because that was the same account. The Google project was also suspended, terminating all servers and the DNS records for the domain, which were using Google nameservers.
That meant it was impossible to do the Google account recovery process, which relied on adding records to the domain to prove we owned it.
It was also impossible for me to open a support ticket without being able to log in or access the domain.
Thankfully, we had another account on the project that was still able to log in and open the ticket.
It was really a terrible experience. The moral of the story is you can't rely on one provider for everything, especially if they don't have accessible customer support.
Google really should not algorithmically blow away a corporate account in good standing without some notice and cure period offered.