I feel like this is tough to do in a way that isn't running into antipatterns. If it's a webapp then you can always deploy the newest code out to all users. If it's a desktop app then you can create processes to auto update the application on start up. A word of warning - users, especially enterprise users, may get angry if their programs change out from under them too much.
Hi Matt thank you for answering. My team and I have a web application made with Angular 4.4.7 ; i agree with your suggestion about the deployment of the new code, but the problem comes when some users logged in(for different reasons) never refresh the browser and they are still able to make requests to the server using the older version. We are trying to handle this issue the best way possible so if you have another suggestion i will be happy to read you. Thank you so much.
If the issue is backend code you could use semantic versioning. Have new users use /v2/api/... and old users use /v1/api/... for example. Or is it that frontend code changes drastically?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I feel like this is tough to do in a way that isn't running into antipatterns. If it's a webapp then you can always deploy the newest code out to all users. If it's a desktop app then you can create processes to auto update the application on start up. A word of warning - users, especially enterprise users, may get angry if their programs change out from under them too much.
Hi Matt thank you for answering. My team and I have a web application made with Angular 4.4.7 ; i agree with your suggestion about the deployment of the new code, but the problem comes when some users logged in(for different reasons) never refresh the browser and they are still able to make requests to the server using the older version. We are trying to handle this issue the best way possible so if you have another suggestion i will be happy to read you. Thank you so much.
If the issue is backend code you could use semantic versioning. Have new users use /v2/api/... and old users use /v1/api/... for example. Or is it that frontend code changes drastically?