Encrypted Offline Cache (EOC) is the mechanism that is used for storing the repeated and the most sensitive data, which is used in the client's application.

Encrypted Offline Cache is precisely known as EOC. It permits a flexible on-device data storage procedure for Android, iOS, BlackBerry, and Windows. This procedure provides a better alternative to the user for storing the manipulated data or the fetched response using the defined adapter data when offline and synchronizing the data for the usage of the server, which provides modifications that were completely developed when offline or without Internet connectivity. In order to dedicatedly create any mobile application for multiple platforms such as iOS and Android, consider using JSONStore rather than EOC. It seems to be much more practical to implement and is supposed to be the best practices of IBM. The JSONStore provides a mechanism to ease cryptographic procedures for encrypting forms and implementing security. PBKDF2 is a key derivation function that would act as the password to access encrypted data, which would be provided by the user. HTML5 cache can be used in EOC, which is not guaranteed to be persistent and is not a proper solution for the future updated versions of iOS.

You can also extend the utilization of JSONStore with its capable features to get the most consistent and secure on-device data storage mechanism for the client's application. Moving with the experience of using EOC, it would be much easier to implement and a way with improved persistent storage procedure for on-dive. In addition to this, the JSONStore holds an aptitude to inhabit and deploy data from custom employment of consuming an adapter on the desired server. The cache allows to use the HTML5 local storage for holding user data. As far as the storage size limit is concerned, HTML5 consumes a limit of 4 to 5 MB, which is supposed to be similar to approximately around 1.3 MB of unencrypted data. If the data appears to surpass the distinct limit, the comportment is undefined. You might experience interruption or delay in handling the data; it occurs when the data is in a huge amount and at the threshold limit.

The following exceptions can be thrown by the WL.EncryptedCache methods: