[eluser]TheFuzzy0ne[/eluser]
Oh I see. I can't comment on typical procedure, but only what makes sense to me.
The main issue I can see is with passing data between pages. Once it's been validated and passed, you shouldn't have to validate it again, which is why it makes sense to store it in the database. Obviously we could use flash data, but there's no guarantee the user is using cookies, although they will most likely be logged in.
I guess it depends on the purpose and the tools that are available, so I will go out on a limb and go as far as to say there is no "typical" way to do this. I believe it's purely circumstantial.
As for a solution to your previous post. I would go with some kind of table in your database to store temporary data, and a script that deletes any data older than a few hours or so. If it's secure data, wouldn't trust the user with it (although if the cookie is encrypted, they shouldn't be a problem), which means it should ideally never leave your server. Also, while the user may not be able to change your cookie as such, there's nothing stopping them deleting it, which may break your application.
Hope this helps, even though I know I haven't been able answer your original query.