rfc:session-gc
Differences
This shows you the differences between two versions of the page.
rfc:session-gc [2016/04/08 09:24] yohgaki Add bug report of mine |
rfc:session-gc [2017/09/22 13:28] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== PHP RFC: Add session_gc() ====== | ||
- | * Version: 0.9 | ||
- | * Create Date: 2014-03-13 | ||
- | * Modify Date: 2016-04-07 | ||
- | * Author: Yasuo Ohgaki, yohgaki@ohgaki.net | ||
- | * Status: Discussion | ||
- | * First Published at: http:// | ||
- | |||
- | |||
- | ===== Introduction ===== | ||
- | |||
- | Current session GC depends on probability. Thus, low traffic sites would not delete expired session data and could be usable as valid session. Traffic varies day and night time for high traffic sites. Chances are high that expired session may not be deleted as it should. | ||
- | |||
- | The best way to purge old session data is executing GC periodically. | ||
- | |||
- | ===== Proposal ===== | ||
- | |||
- | * Add session_gc() API. | ||
- | * Document calling session_gc() periodically is the best practice. | ||
- | |||
- | |||
- | int session_gc(void) | ||
- | |||
- | It simply executes GC save handler defined. | ||
- | |||
- | |||
- | ===== Backward Incompatible Changes ===== | ||
- | |||
- | None | ||
- | |||
- | ===== Proposed PHP Version(s) ===== | ||
- | |||
- | PHP 7.1 | ||
- | |||
- | ===== Vote ===== | ||
- | |||
- | VOTE: 2016/04/08 - 2016/04/15 | ||
- | |||
- | <doodle title=" | ||
- | * Yes | ||
- | * No | ||
- | </ | ||
- | |||
- | This project requires a 2/3 majority. | ||
- | |||
- | ===== Patches and Tests ===== | ||
- | |||
- | * https:// | ||
- | |||
- | ===== Implementation ===== | ||
- | |||
- | After the project is implemented, | ||
- | - the version(s) it was merged to | ||
- | - a link to the git commit(s) | ||
- | - a link to the PHP manual entry for the feature | ||
- | |||
- | ===== References ===== | ||
- | |||
- | * https:// |
rfc/session-gc.txt · Last modified: 2017/09/22 13:28 (external edit)