Andoid synchronized, volatile is it necessary?

Question

Java

The application uses a class that stores all the data that is taken from the network. For almost every action, we go to the Internet through AsyncTask, parse the response and put it into this class. Naturally, since each request to the server goes in a separate thread and then saves this data, the next one running on a different core can see the old data. Am I right or does AsyncTask solve this problem somehow?

Answer 1

0_o How can AsyncTask affect the behavior of your class at all?
In any case, you should always build the correct architecture of your application, including keeping track of the race condition.