AJAX and CI Session (v1.7) w/DB

[eluser]drewbee[/eluser]
Unfortunately for me, this was not an option. To me it was clearly a bug and I have made my own session class to take care of this.

My session class currently only makes two total queries, on each and every page load. sess_read for the initial session data, and during the __destruct() will update any changed data.

I also changed the sess_time_to_update to work within this very last update, however I will still see the same results if the AJAX call is the one to hit the expiry time.

I will probably have to come up with a way to notify ajax calls to force the session to not regenerate the id, and leave it strictly for main browser calls unfortunately.