Session/application variables

Results 1 to 4 of 4

Thread: Session/application variables

  1. #1
    Join Date
    Dec 1969

    Default Session/application variables

    Where session and application variables stored...<BR>so how does it affect the perfomance of asp page.<BR>which (server or client) has to suffer from the overhead of these variables.....<BR><BR>Please by hurry.<BR><BR>Give answer at

  2. #2
    Panos Barbalias Guest

    Default RE: Session/application variables

    Basically Sessions are stored and maintained for each visitor of the site at the web server. Clients don&#039t suffer from them, since the web server actually sends pure HTML to our browsers. The main traffic is created in the server.

  3. #3
    Sandeep.R Guest

    Default RE: Session/application variables

    Hey man, <BR>Session and Application variables are stored as Temporory Cookies. It&#039s like when you say Session("UserID") = "xxx" then a cookie is wriiten on to the Client machine. this is a temporory cookie, which can be destroyed by Program, abandoning the Session. But when you close the browser it waits for 20 min and kills itself. <BR>If the Client has said no to cookie then you cannoit write anything to his machine, so then is the problem

  4. #4
    Rhodes Guest

    Default no they're not....

    The only cookie that is written is the session ID. Session variables are stored in memory and require this cookie to know which client the variables belong to. Application variables are also stored in memory, but do not require the cookie since all users share application variables (not client specific).<BR><BR>Because the variables are stored in memory, it is a good idea not to use too many. For better performance, consider using the session ID cookie as a primary key in a table, and define session variables within that table.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts