Ferreteria/v0.5/@cls/login/csLogin/IsLoggedIn: Difference between revisions
< Ferreteria | v0.5 | @cls | login
Jump to navigation
Jump to search
(Created page with "==About== * '''File''': {{l/ferreteria/code|login/status.php}} * '''Returns''': TRUE iff all of the following are: ** Session is valid ** Session's Account ID is set ** Sessio...") |
No edit summary |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{page/ferret/method}} | |||
==About== | ==About== | ||
* '''Returns''': TRUE iff all of the following are: | * '''Returns''': TRUE iff all of the following are: | ||
** Session is valid | ** Session is valid | ||
| Line 8: | Line 8: | ||
** If there's no Session Status, creates a blank one. | ** If there's no Session Status, creates a blank one. | ||
** Return value depends on the Session having an Account ID set. | ** Return value depends on the Session having an Account ID set. | ||
==Thinking== | |||
The user can be in a logged-in state under either of these conditions: | |||
* The user has just successfully submitted valid login credentials. | |||
* The user's browser has submitted a valid Session cookie. | |||
We need to allow for either of these to be true. (If neither is true, then the user is '''not''' logged in.) | |||
==History== | |||
{| class="wikitable sortable" | |||
|- | |||
! when || what | |||
|- | |||
| '''2023-04-02''' || Actually, why not let the Storage Card do some calculations, where that makes sense? That definitely reduces the complicatednessity of looking up the Native Card. | |||
|} | |||
Latest revision as of 14:45, 2 April 2023
|
Ferreteria:
ferret\login\csLogin::IsLoggedIn() |
About
- Returns: TRUE iff all of the following are:
- Session is valid
- Session's Account ID is set
- Session's Account ID is not NULL
- Action:
- If there's no Session Status, creates a blank one.
- Return value depends on the Session having an Account ID set.
Thinking
The user can be in a logged-in state under either of these conditions:
- The user has just successfully submitted valid login credentials.
- The user's browser has submitted a valid Session cookie.
We need to allow for either of these to be true. (If neither is true, then the user is not logged in.)
History
| when | what |
|---|---|
| 2023-04-02 | Actually, why not let the Storage Card do some calculations, where that makes sense? That definitely reduces the complicatednessity of looking up the Native Card. |