| Confusing Session Class change |
Hi,
This might be one for the admins/devs at BCIT but I'm confused about the apparent backtrack in the way we're handling session data from v2 to v3. As far as I was aware when using v2, best practice was to use the Session Class for everything (creating, amending, reading, deleting/unsetting). In fact the documentation evens reads "Note: The Session class does not utilize native PHP sessions. It generates its own session data, offering more flexibility for developers." However when reading the new documentation it looks like we're being given two options (support for the old v2 way and hinting at using the traditional method [$_SESSION]) - this makes me think that by the time the next big release comes out we'll be expected to use only $_SESSIONs. I'm fine with this, just wondering if I could get some clarification on the subject? As far as I can tell from looking through the new docs, this class has had the biggest overhaul. Thanks for any contributions. |
| Messages In This Thread |
|
Confusing Session Class change - by natefrogg028 - 12-30-2015, 05:06 PM
RE: Confusing Session Class change - by skunkbad - 12-30-2015, 05:51 PM
RE: Confusing Session Class change - by kilishan - 12-30-2015, 09:33 PM
RE: Confusing Session Class change - by natefrogg028 - 12-31-2015, 04:41 AM
RE: Confusing Session Class change - by mike7418 - 12-31-2015, 05:06 AM
RE: Confusing Session Class change - by natefrogg028 - 12-31-2015, 10:29 AM
RE: Confusing Session Class change - by mike7418 - 12-31-2015, 04:06 PM
RE: Confusing Session Class change - by mwhitney - 12-31-2015, 11:37 AM
RE: Confusing Session Class change - by Narf - 12-31-2015, 08:21 PM
|
