[eluser]allibubba[/eluser]
thanks Mirage, i'll look a bit more into hooks, still learning the CI framework.
just checked and my current solution does not survive a failed login... but when using flash data i need to continually keep it alive eg:
keep_flashdata(); which means i have to have that in each function of my login/out check user process, which does seem like the wrong way to do things.
i kinda like the idea of setting and updating a cookie, but will look further into using the header() function. just that updating a cookie means i have to load a model and run a cookie update function for every view change, so maybe see if i can work something out with hooks. trying to follow 'DRY' (don't repeat yourself) principals as much as possible.
as for JS, yeah i completely agree (didn't want to start a debate on how many people do/don't use js), but for this round of exploration i want to do everything through CI, once i have a solid grasp of CI i'll be rebuilding with a robust JS front-end with mootools, but will also degrade to native CI functions if JS is disabled.
