While using FLUX in a CRUD application, according to what i understood, initially the data is returned from an AJAX call and then stored in the STORE. So, all the data that is currently viewed is only from the STORE. So my question is, if I'm seeing a listing page of all the data and some other user changes that data in the server, wouldn't i have to use an AJAX call again to list all the data and then again store in the STORE? What would be the point of using STORE if i have to call again?

I saw a tutorial where initially on the page load, the data gets rendered and after that everything is done with the data in the STORE. But with this, if the server data changes by some other users, wouldnt i have to fully reload the page again? I seem to have a lot of confusion regarding this issue.

What is the use of FLUX and how is it implemented? Also  , what is the correct way of implementing it in a CRUD application?

While using FLUX in a CRUD application, according to what I understood, initially the data is returned from an AJAX call and then stored in the STORE. So, all the data that is currently viewed is only from the STORE.

So my question is, if I'm seeing a listing page of all the data and some other user changes that data in the server, wouldn't I have to use an AJAX call again to list all the data and then again store in the STORE? What would be the point of using STORE if I have to call again?

I saw a tutorial where initially on the page load, the data gets rendered and after that everything is done with the data in the STORE. But with this, if the server data changes by some other users, wouldn't I have to fully reload the page again? I seem to have a lot of confusion regarding this issue.

What is the use of FLUX and how is it implemented? Also, what is the correct way of implementing it in a CRUD application?