Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have two questions:
Would it be significantly slower to have a class for sessions in PHP? I mean, nearly duplicate with the current $_SESSIONS, except it’s handled by a class using file IO, un/serialize, cookies and so forth… I’m just having issues with how PHP handles it’s sessions.
Is it bad to have lots of files in one directory? Around 50k or 60k? Should I use a database or merge them into a lesser amount of files, or is it unnecessary?
It wouldn’t be slower if properly designed, but i would highly recommend that you do not do that. Reinventing the wheel is never a good option. Thousands of people have already worked on PHP sessions and code written by thousands is by far less error prone than individually written code. You need to be knowledgeable of too many things to implement your own sessions system(including security etc..).
Generally speaking, files are faster for sequential data. However, a database is much more flexible and at times can be faster. I would personally use a database for sure. Messing with so many files would require that you write a whole frontend system. Why would you want to mess with that when a dbms offers that out of the box ?