Native sessions or CI sessions.

[eluser]EugeneS[/eluser]
exactly, if some one asking for such a things it is most likely that his application wont require all of the benefits of the completely database driven site, his database wont be located in the dedicated DB cluster etc... most likely his application will be hosted on the shared hosting where database load and query execution is very important and time taking ... thats why in case your application not smth like yahoo and hosting budget not at least several hundreds per month (at least to have 2 separate servers) then no reasons to store session in the database ....

more over routine described by you absolutely applicable and to the database driven sessions - no difference where to store in case of security lack ...

in case of use CI session handling libraries - i would suggest to use popular native session library ...

to the topic starter:
forget about encrypted cookies at all ...
in case of shared hosting forget about database driven session implementation ...

better use native session implementation library ...