Follow us on Twitter!
Hacking isn't just Computers & Exploits. It's a Philosophy. - Mr_Cheese
Friday, April 25, 2014
Navigation
Home
HellBoundHackers Main:
HellBoundHackers Find:
HellBoundHackers Information:
Learn
Communicate
Submit
Shop
Challenges
HellBoundHackers Exploit:
HellBoundHackers Programming:
HellBoundHackers Think:
HellBoundHackers Track:
HellBoundHackers Patch:
HellBoundHackers Other:
HellBoundHackers Need Help?
Other
Members Online
Total Online: 21
Guests Online: 21
Members Online: 0

Registered Members: 82908
Newest Member: krishna7799
Latest Articles
View Thread

HellBound Hackers | Computer General | Hacking in general

Author

Potential Problems With Persistent Connections & Regenerating Sessions


Member

Your avatar

Posts:
Location:
Joined: 01.01.70
Rank:
Guest
Posted on 26-07-09 02:57
Are there any potential problems or obstacles to be aware of when using MySQL persistent connections or regenerating sessions through the PHP function session_regenerate_id() ?

I read somewhere that using session_regenerate_id() could be a problem because it leaves the old session data "open" and it holds up other scripts that are trying to access that page. I don't want my pages to load one by one, meaning that one user has to wait for another user's page to fully load before his loads. However I'm unsure about that and I need someone to verify this claim.

Also, what are the pros and cons of using persistent connections with MySQL?

As far as I know, it's a persistent connection when you connect to the database but do not use mysql_close to close the connection. I also heard that this could come in conflict with the max connections because if more than 200 users (or whatever the max connection option is set to), then MySQL will reject all other connections. Anyway, I don't know much about that either.

So... problems of persistent connections and regenerating sessions?

Edited by rex_mundi on 11-12-13 13:45