Dealing with releases of single page applications • Hacker News Board

Re: Dealing with releases of single page applications

#11

Post by davidjnelson » Sat, Mar 12, 2016, 2:54 AM UTC

hankeypancake wrote: post #9

swalsh wrote: post #5

If this was a problem I was truly concerned about, i'd attack it with discipline and tinkle bit of versioning. If you're making a breaking change to the API perhaps you should increment the major version, and support both, and then sail away the old API when you feel comfortable doing so. yoursite.com/api/v1/call yoursite.com/api/v2/call

Yes, api versioning would be nice. However, with limited resources (as always) this takes you very far without it. Api versioning also only handles breaking api changes (which this doesn't really protect you from, depending on how the users act to the notification), this also notifies the users to refresh their browsers for hotpatches regarding the frontend, and also regular feature releases. So even if you have api…

Seems like graphql would solve the api versioning problem pretty well.

Re: Dealing with releases of single page applications

#12

Post by hankeypancake » Mon, Mar 14, 2016, 12:23 PM UTC

davidjnelson wrote: post #10

Cool idea and article. Hot reloading deployed production applications is a really intriguing feature of meteor. I'll bet something similar could be built if someone was using react and redux. Sort of like the local development hot reloading with react-transform-hmr, but running in production. This would make it automatic instead of requiring a browser reload and erasing the users current ui state. The trick would be…

Agree on all points. We don't automatically reload the browser though, so it's up to the user to actually get the new version, otherwise people would be very angry with us..

The main reason we did it this way, is that it is really really simple and quick to implement.

Thanks for the input!

Re: Dealing with releases of single page applications

#13

Post by hankeypancake » Mon, Mar 14, 2016, 12:33 PM UTC

th0br0 wrote: post #6

Why not simply edit the HTML5 appcache manifest? (i.e. add a commented-out timestamp)

I'm not very familiar with appcache, but reading a bit about the specifics it looks like it would work fine as long as you don't need IE<=9 support. Thanks for the input!