Timeline for Review on my current structure and tips on improvement
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:48 | history | edited | CommunityBot |
replaced http://crypto.stackexchange.com/ with https://crypto.stackexchange.com/
|
|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Dec 1, 2011 at 7:05 | vote | accept | John | ||
| Nov 30, 2011 at 12:09 | history | edited | yannis | CC BY-SA 3.0 |
added 1293 characters in body
|
| Nov 30, 2011 at 11:57 | comment | added | yannis | If you are unsure, you shouldn't try and convert it. Study OO concepts a bit and then start coding. The bad thing with OO is that there isn't a "one fits all" solution. You could have a Session class (for token etc), and a User class... And a validation class... it depends on what the concerns & responsibilities are (en.wikipedia.org/wiki/Single_responsibility_principle)... As for the individual salt, you can post a question at crypto.stackexchange.com for more educated answers, mine was mostly empirical. | |
| Nov 30, 2011 at 11:54 | comment | added | John | Also, If u look at my updated question - How would I treat the following code there in OO? As, that "file" is called from an AJAX request, to check the username.. | |
| Nov 30, 2011 at 11:52 | comment | added | John | I have always thought that a individual salt was more appropriated, I guess not. About OO, yes, I've considered that, but I'm quite unsure of how I should do it. A User class, I assume, but should I put the validation in the method, or have a method for validation or a class for validation? | |
| Nov 30, 2011 at 11:45 | history | edited | yannis | CC BY-SA 3.0 |
added 194 characters in body
|
| Nov 30, 2011 at 11:32 | history | answered | yannis | CC BY-SA 3.0 |