rfc:not_serializable
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| rfc:not_serializable [2023/12/09 11:54] – maxsem | rfc:not_serializable [2023/12/09 12:30] – maxsem | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== PHP RFC: # | ====== PHP RFC: # | ||
| * Version: 1.0 | * Version: 1.0 | ||
| - | * Date: 20123-11-26 | + | * Date: 2023-11-26 |
| * Author: Max Semenik, maxsem.wiki@gmail.com | * Author: Max Semenik, maxsem.wiki@gmail.com | ||
| - | * Status: | + | * Status: |
| * First Published at: http:// | * First Published at: http:// | ||
| Line 26: | Line 26: | ||
| </ | </ | ||
| - | Not only is this method bulky, it's also less readable. It also lacks a way for various code analysers | + | Not only is this method bulky, it's also less readable. It also lacks a way to indicate the intention to various code analysers |
| ===== Analysis ===== | ===== Analysis ===== | ||
| Line 37: | Line 37: | ||
| * Wrappers for all the above. Imagine a PDO wrapper that creates connections on demand. If the connection hasn't been established yet, its serialization will succeed, which results in unpredictable behavior. | * Wrappers for all the above. Imagine a PDO wrapper that creates connections on demand. If the connection hasn't been established yet, its serialization will succeed, which results in unpredictable behavior. | ||
| * Secret information that shouldn' | * Secret information that shouldn' | ||
| - | * Security-sensitive classes that are unsafe to unserialize with arbitrary data. | + | * Security-sensitive classes that are unsafe to unserialize with arbitrary data ([[https:// |
| ===== Proposal ===== | ===== Proposal ===== | ||
rfc/not_serializable.txt · Last modified: 2023/12/10 12:31 by maxsem