-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to handle the version property in react or angular frontend? #86
Comments
Hi. If things are asynchronous things get a bit harder. Then the client need to subscribe to events from the server. This can be done using websockets, signalr or similar tech to get updates as they happen. I have used both options myself and giving events can be a nice way to notify that something has changed on the server by an other user as well. But it's more work. Hope this helps a bit. |
Thank you for the fast reply. We now implemented indeed the "refresh" option. So get the user again and update the field. Just like you would open the page. In this way you don't have to write client business logic for something that the server maybe already have done for you. in example: We were also thinking about websockets or signalr but in a later fase of the application. Now first other priorities. |
Sounds good. I'm closing this as I hope you got answers to your questions. Just reach out again if theres any more questions. |
Hi, we want some advice.
We are creating a new application that has a react frontend. In this frontend we have in example the details page of an entity. In example the entity customer. Let's say we can edit a field of a customer (in example phone number) so we have a popup that will let the user enter the new phone number. The phone number is pushed to the server with the latest version and command is executed.
But what then? Do we need to update the version on the client? Or are we refreshing the page? Or are we (re)loading the customer again so we get the latest version?
How are you guys doing this?
Thanks
The text was updated successfully, but these errors were encountered: