i'm wondering when should i not store Objects in Sessions?
i'm working on a user-driven system, and i need to define messages for example, after login "Welcome back User", or on wrong login information, and these messages they have a different types "error,succes,warning, etc..." so i created a controller for it, i create a new object from that Message class, attach it as Serialized to the View, and the view unserializes it, and then removes it from the session.
I'm just having a feeling that im making a mistake here, is it ok to use this method from a performance perspective, what security issues can be with it, and does the object remain in the server-side memory? or should i handle flushing it as well?