Sessions dilemma.

[eluser]voltechs[/eluser]
Hey guys.

CI's session management, (despite claims in its user guide) is not flexible. For me anyway.

See, I'm building a "plugin" for the community, so I wanted to use the built-in support for sessions due to the likely hood of users using them. I wouldn't want to write a plugin that, in order to install it, you would have to create a folder and give it the correct permissions just so that the plugin would work. I can't count on users having that kind of access to their servers (or can I?) so that was my reason for going with CodeIgniters sessions (little did I know it's just a cookie, not really a session). Anyway, I guess this simple fact is what prevents me from performing various fancy-footwork to get things done in an "elegant" fashion.

So it really boils down to being between a rock and a hard place. I could either require users to create a "sessions" folder, and give it the correct permissions and everything would work handy-dandy with my own implementation and management of sessions, or I could stick with CI's sessions and have to live with various bugs throughout the plugin (such as the user getting logged out when I try to update the session data from various parts of the app). Anyway, more of a question of opinions, but heck, if you have any solutions, lemmy at em!

I won't dismiss the possibility that I'm crazy.

Cheers!

-- volte

P.S. this may become completely moot, as I am debating expanding the plug-in into a full-fledged CI app. I'll have everyone weigh in when I release the beta here shortly.

EDIT: Woot! http://www.codeigniter.com/wiki/Native_session/

I'm leaning more and more to a full-fledged app, but dang, thats really not what this plugin was originally targeting :/