in reply to Understanding the Use of Session Variables

Conceptually, “session variables” are a pool of persistent information that is stored on the host, in such a way that they can be quickly retrieved and updated with each incoming request.

The session information is located using some kind of random identifier, customarily stored as a “cookie,” or as a hidden form-field, or as a part of the URL information, or some combination of the foregoing.

Customarily, these mechanisms are used only to transport a random identifier, which is not ”trusted” but rather is subjected to rigorous validation. The client-side is never trusted as a source of original information.

As you peruse the various session-handling modules on CPAN, you will observe how they typically separate the various concerns ... session identification, the transport of the session-identifier between client and host, and session storage. This will give you the flexibility to configure exactly what is needed for your particular application, and to change it in the future if necessary.

I, too, would judge that you have not yet taken the time to avail yourself of the introductory materials to which you, have at several times, thus far been pointed . . . Take care not to waste our time, nor your own!

Replies are listed 'Best First'.
Re^2: Understanding the Use of Session Variables
by spickles (Scribe) on Mar 06, 2009 at 04:08 UTC
    Thanks everyone for the replies. While it is obvious to me I have MORE research to do b/c I don't yet understand all of the pieces, what I also don't understand is the attitude from some of you that I am wasting your time:

    I, too, would judge that you have not yet taken the time to avail yourself of the introductory materials to which you, have at several times, thus far been pointed . . . Take care not to waste our time, nor your own!

    I am NOT a programmer. I am a Systems Engineer and design networks. If some of you can read the tutorials and understand it the first time around, good for you. But that does not give you the right to assume that I am here just to pass the work off to someone else to figure things out for me. I HAVE read several different tutorials, and the fact that I STILL need help doesn't mean you should assume I haven't tried anything on my own. I have figured out many of my programming issues on my own, and have come to the conclusion that cookies should work better for me after completely reworking my code to support first GET and then POST. For those of you that are willing to help others work through their problems, post a reply. For those of you that want to make a negative comment regarding the fact that I have read a lot on the subject and still don't understand it, keep your replies to yourselves.
      Sorry spickles, but you can't control other people, its best not to fret over that.

      Instead of split, use CGI's url_param, see MIXING_POST_AND_URL_PARAMETERS

        Anonymous Monk -
        Thanks for your kind response. Those other responses just make me feel horrible because I know how hard I work to figure things out on my own, and then I essentially get people calling me stupid because I can't figure it out from the document. I'm sure you're familiar with the acronym 'RTFM'... I did, I promise!! I appreciated your link to CGI.pm on CPAN. It's got lots of information that I can use to clean up my code.