Timeline for Login Validation
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 17, 2012 at 19:45 | comment | added | Jeff Davidson | I've updated my post check out EDIT 2! | |
| Jan 16, 2012 at 21:37 | comment | added | palacsint | 1, It would improve code readability and help maintainability a lot. The key words are encapsulation and high cohesion. It makes possible to change the implementation without changing the code of the clients. If you haven't read yet read Clean Code by Robert C. Martin. 2, Sorry, I don't know CI. It maybe worth a question on SO. | |
| Jan 16, 2012 at 19:37 | history | bounty awarded | CommunityBot | ||
| Jan 9, 2012 at 17:00 | comment | added | Jeff Davidson | 3. I already have a function for storing session data in the database | |
| Jan 9, 2012 at 16:54 | comment | added | Jeff Davidson | So your saying: 1. I should do a function for isUserBanned, isUserSuspended, isUserActived, all of the rest of those? Also why would I need to make a function for the lock_date and flags if its only going to be like 2-3 lines. 2. Thank you I'll do that. But with CI what file would I put that in? 3. I'll do that as well. | |
| Jan 9, 2012 at 12:37 | history | answered | palacsint | CC BY-SA 3.0 |