LocalStorage (2), weblocalstorage

LocalStorage (2), weblocalstorage

I have been busy recently and it will be very late when I come back. I don't want to go to bed because Red Bull drinks too much (the company gives me free of charge, a lot of boxes of o ), when I can't sleep, I want to visit the blog Park. I recently am busy working on a singlePage application that imitates native apps, the brothers in the background recently said that it was too slow for me to open the website (my brother is a webpage rather than a native App, and of course it should be slow). No way, I had to go to the blog Park to find a breakthrough point, coincidentally, I saw a bull share a black Technology in my blog: I used js to break through the Local Storage Capacity Limit and save the whole site resources to the user's local location for offline browsing. I immediately downloaded the Demo of Daniel, and the code was really good. I didn't use any plug-ins. I understood the principle and saved static resources to other domain names through cross-origin. However, this technology is still quite a long time ago. Specifically, this is not a new technology, but a rule vulnerability in HTML5, A few years ago, a foreign bull used the HTML5 rule vulnerability to attack a user's disk, resulting in a vulnerability that was raised after the user's disk became crowded for a short time. Fortunately, no website in China is so dark that it's okay to squeeze other hard drives. This shows that our internet environment in China is still friendly. Experts are either working overtime or starting a business, busy making money from products for financing, huh, huh ......

Let's get down to the truth. Before that, I wrote an article about localstorage. The content mentioned that localstorage is 5 MB in size. However, with the upgrade of the browser, this value actually doesn't make much sense, especially on the mobile end, let me give you a few examples, for example, Android2.3. Its Local Storage ceiling is 8 MB, and Android4 has risen to 58M, prices are faster than those in Shenzhen! Let's talk about ios and iPhone 4 in a well-behaved manner of 5 M and iPhone 5 in 26M. We can imagine what the iPhone 6 s is like.

Therefore, most of our mobile websites are small in size and can be used without cross-domain communication. Now we can use them more effectively. So I want to keep a learning attitude to learn the principle of this cross-origin storage technology, because I want to continue watching whether the storage limit for a single domain name in the mobile phone field will continue to increase. If yes, cross-domain Storage is not required, it is more convenient to manage localstorage within a domain name.

OK. I wish my friends in the garden a good night and a good dream. I slept first.