Timeline for PHP Parallel Requests and Session Stability
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2012 at 0:26 | comment | added | yannis |
@BradKoch Yes, that's the short version. For a low traffic site, file based sessions are perfectly acceptable and usually any concurrency issues go away if you remember to session_write_close() after you finished using $_SESSION. Just don't do the mistake I did and use $_SESSION for caching.
|
|
| Jun 14, 2012 at 22:47 | vote | accept | Brad Koch | ||
| Jun 14, 2012 at 22:47 | vote | accept | Brad Koch | ||
| Jun 14, 2012 at 22:47 | |||||
| Jun 14, 2012 at 22:47 | comment | added | Brad Koch | In short, lock sessions, end the lock as quick as possible, try alternative session backends, and accept a bit of serialization? Thanks for the thorough answer to a rather open ended question, btw. | |
| Jun 14, 2012 at 21:11 | history | edited | yannis | CC BY-SA 3.0 |
added 512 characters in body
|
| Jun 13, 2012 at 22:16 | comment | added | grossvogel | +1 If you keep the session locking as brief as possible and treat session data as mostly read-only, you shouldn't need a hardcore concurrency solution unless you're doing something unusual. | |
| Jun 13, 2012 at 22:04 | history | answered | yannis | CC BY-SA 3.0 |