Big upgrade tonight

[Jeff Lindsay]

Tonight I'm going to deploy some major changes that will make all old clients (with the smiley face) stop working. Those clients *should* start getting a notification every 5 minutes after the deploy that says more or less "the client is no longer valid, click to upgrade" which will take them to the download page for the latest client. 

Behind the scenes, all requests to api.notify.io will be going to App Engine. Listen requests will either return the notification above and hold for 20 seconds (since the old client would reconnect immediately when a request finished), or it will redirect to the new Realtime backend if you're using the new client. This means old ListenURLs will continue to work if you have the new client. 

The notify endpoint should behave exactly as before (if not better).

After this, our uptime will improve dramatically. Hunter is also working on a status page in case there are outages. 

--
Jeff Lindsay
http://progrium.com

[Brian Dunnington]

for those of using an alternative client, what is the best way to test
whether or not it will continue working after the cut over?

[Jeff Lindsay]

We'll have to start tracking alternate clients like yours to make sure I can work with you in upgrades like this. It should be fine if you follow standard HTTP redirects. If not, we'll have to come up with something. I mentioned a while back clients should follow redirects knowing this day would come. We should probably also formalize *some* kind of guidelines for 3rd party clients. 

[Brian Dunnington]

yeah, my client follows redirects and currently works with old style
and new style listen urls. just wanted to know if there was anything
else to be worried about or if there was a way to try the scenario
before hand somehow. sounds like it will be covered, so i will check
it out later tonight after the changes are made and make sure
everything looks good.

thanks.