![]() To learn more about the advantages and disadvantages of online and offline modes, consider also the following resources: The offline client typically does not show any delays at all. Occasionally, due to various connection hiccups, it can last longer, and every now and then you will wait a lot longer only to receive broken connection error. Getting one server response (many screens need multiple requests) usually takes 0.1 - 0.5 seconds. However, the device battery will feel increased data processing.Īs a rule of thumb, users in online mode experience similar response times to a web browser. Fortunately, this bloated protocol is wonderfully compressible hence it does not impact the network traffic that much. Typically, 90% of the data sent is an overhead. ![]() In other words, the protocol used for client-server communication is extremely bloated. Here is a small illustration: When the server sends the information about when a particular record was created, it actually sends an XML string similar to this: While most readers intuitively understand the above differences, some may not realize how inefficient the client-server communication is. However, even in online mode, synchronization is necessary in the case of updated app projects, to download new customization. One of the advantages of the online mode is that it does not need data synchronization. Increased internet traffic (the same data is sent again and again).These are some of the disadvantages of the online mode: The online mode uses a remote database (located at the server), hence all data operations are slow, costly, and potentially risky (depending on the quality of your internet connection).What is difficult – is the (occasional) synchronization between the local and remote databases. The offline mode keeps the data in the local database hence the data loading/storing is fast and presents no problem at all.The big difference between both modes is immediately clear – the data storage: As part of this process, all changes that you have made (stored in the change log) are uploaded to the server and potential new data is downloaded from the server and stored locally. Additionally, the account record is marked as “dirty” (this information is stored in the change log) so that the change can be later sent to the server.Įvery now and then, you have to synchronize the local device with the server. Once you're done editing, the changes are saved to the database.When you open the account, full account data is loaded from the database.Again, as you scroll down the list, additional pages are read. ![]()
0 Comments
Leave a Reply. |