Timeline for Storing large data in HTTP Session (Java Application)
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Dec 17, 2013 at 21:15 | answer | added | Mr. Shiny and New 安宇 | timeline score: 3 | |
| Oct 18, 2013 at 16:39 | answer | added | jacktrades | timeline score: 1 | |
| Oct 18, 2013 at 2:18 | comment | added | Umesh Awasthi | @MichaelT: That is one of option i was thinking of, but have to cross check it. | |
| Oct 18, 2013 at 2:17 | comment | added | Umesh Awasthi | @amon: generally session data is stored as heap size allocated to JVM.Though container can write session data to disk, but only when low in memory. | |
| Oct 17, 2013 at 19:33 | comment | added | user40980 | I believe that typically one uses a cache (ehcache for example) between the database and the server. The cache tends to be a bit more intelligent with fetching and storing data rather than trying to put it all in the session. | |
| Oct 17, 2013 at 19:10 | comment | added | amon | Could you specify what exactly you mean with “saving to HTTP session”? Cookies, local storage in the browser, your database, or something completely different? | |
| Oct 17, 2013 at 18:49 | history | asked | Umesh Awasthi | CC BY-SA 3.0 |