티스토리 뷰
1. Web Storage API
2. Cache Storage API
3. Indexed DB
It can have large amount of data
4. Session Storage
SessionStorage is tab specific, and scoped to the lifetime of the tab. It may be useful for storing small amounts of session specific information, for example an IndexedDB key. It should be used with caution because it is synchronous and will block the main thread. It is limited to about 5MB and can contain only strings. Because it is tab specific, it is not accessible from web workers or service workers.
5. Local Storage
LocalStorage should be avoided because it is synchronous and will block the main thread. It is limited to about 5MB and can contain only strings. LocalStorage is not accessible from web workers or service workers.
6. Cookies
Cookies have their uses, but should not be used for storage. Cookies are sent with every HTTP request, so storing anything more than a small amount of data will significantly increase the size of every web request. They are synchronous, and are not accessible from web workers. Like LocalStorage and SessionStorage, cookies are limited to only strings.
7. Native File System API
The Native File System API was designed to make it easy for users to read and edit files on their local file system. The user must grant permission before a page can read or write to any local file, and permissions are not persisted across sessions.
- Total
- Today
- Yesterday
- aws
- ASCII
- Lombok
- 메모리 릭
- SQL 전문가 가이드
- sort algorithm
- Git
- ActiveAdmin
- 실용주의
- annotation
- effective-java
- Encoding
- SHA
- 암호화
- Java
- Spring-Boot
- 사고..
- point
- WebClient
- 이펙티브자바
- ruby
- gitignore
- IntelliJ
- querydsl
- 이벤트스토밍
- DesignSystem
- TroubleShooting
- fetchResults
- Generic
- 코테 log
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |