Dave many thanks - and I even had to look up non sequitur.
Unfortunately you have simply prompted me to probe a bit further, and try to get a better understanding from someone who knows.
1) If a new CI instance is associated with a browser what happens if our user clicks on a link in an email which then launches a class and method? Does this count as a GC trigger?
2) If browser comms are stateless what exactly is controlling expiry? Is CI somehow testing the cookie on a timer?
3) If a browser recives a rendered page after logging out from our site (effectively offering a login screen) can I still send flashdata to their screen? ie they still (I think) have an active session. If they have actually closed that browser tab and I try to send flashdata to their session_id as found in the DB, will it be queued for the next request?
I'm sorry if these are demonstrating my ignorance of this technology, but I hope to get much better very soon. Perhaps Iam just missing some vital building blocks ...
regards, Paul
