CI 1.6 sessions

[eluser]EugeneS[/eluser]
[quote author="Edemilson Lima" date="1202852962"]
But there is one thing I want to know: if a web site have thousands of simultaneous requests, can it start a session for every request without blow up the server? Ares sessions based on cookies or database any way better to handle this?[/quote]

lets think.

database is always a thin section in the chain thats why every one trying to optimize his sql queries and thats why so many books were written about good database structures, methodics etc ... database is always slower that web server specially when you have to look through millions of records ... thats why database is not a way at all .... even without encryption. MORE OVER any way we store data in database serialized.

so what is faster serialize unserialize by functions and then write and recreate indexes or search and update or search and unserialize
OR searialize or unserialize by compiled php and open/write file which name is identical to session ID ?

database is not a speed way and only increase execution time and server load.

now about cookies ....
i think no one so stupid to use some private etc data in non encrypted cookie.
so cookie session must be encrypted ... what we have at the moment:

what is faster: encrypt AND decrypt cookie session by script means or serialize AND unserialize array by compiled PHP ... i think php will be faster + we "dont have" limitation, right + we dont have to send a lot of data with our request here and there all the time but just session id ....

so cookie not a way i think as well ...

do not see any flexibility to choose between VERY BAD and VERY BAD way both of them are VERY BAD especially if site is located on shared hosting (i think 90% are on shared hosting)...

so if you have DB cluster or server cluster or at least dedicated server .. go ahead and use DB sessions (even in this case i would never use DB sessions)