[Javascript] Bit late! JavaScript to PHP variable transfer

Chris Tifer christ at saeweb.com
Fri Aug 22 10:50:57 CDT 2003


Ok, I get what you guys are saying now. I understand about SessionIDs, just
wasn't sure that was how the data was accessed on the server - which
explains why if you don't have your cookies, you can't communicate since it
can't look your session up.

Chris Tifer

----- Original Message ----- 
From: "Mike Dougherty" <mdougherty at pbp.com>
To: "'[JavaScript List]'" <javascript at LaTech.edu>
Sent: Friday, August 22, 2003 11:27 AM
Subject: RE: [Javascript] Bit late! JavaScript to PHP variable transfer


> The "session cookie" is just a key used to access the session on the
> server, the actual data is stored on the server.  We use this method to
> cache potentially large ADO recordsets in the session for faster
> successive lookups by the user.  (they suffer a 5-10 minute retrieval,
> then interact with the cached data.  Sure, there's a great deal of
> round-tripping, but it's an intranet and performance isn't <too>
> terrible)
>
> -----Original Message-----
> From: javascript-bounces at LaTech.edu
> [mailto:javascript-bounces at LaTech.edu] On Behalf Of Chris Tifer
> Sent: Friday, August 22, 2003 9:49 AM
> To: [JavaScript List]
> Subject: Re: [Javascript] Bit late! JavaScript to PHP variable transfer
>
>
> I used to believe the same thing, but that's not the case. Disable
> cookies in your browser. Session Variables are indeed cookies
> stored on the client.  Or am I mistaken in that the variable is set on
> the server, but the cookie on the client is just needed to associate
> the variables to the user?
>
> Application Variables are stored on the server for sure...
>
> Chris Tifer
> http://emailajoke.com
>
>
> ----- Original Message ----- 
> From: "Peter Brunone" <peter at brunone.com>
> To: "'[JavaScript List]'" <javascript at LaTech.edu>
> Sent: Friday, August 22, 2003 10:22 AM
> Subject: RE: [Javascript] Bit late! JavaScript to PHP variable transfer
>
>
> > Technical nitpicky point:
> >
> > Session variables aren't cookies; they're stored in memory on
> > the server.  A cookie is the most common method of keeping track of
> > which session is yours, but even that can be bypassed, e.g. with
> Cookie
> > Munger included in the IIS4 reskit, or ASP.NET cookieless sessions.
> >
> > Other than that, I totally agree with you; this is a
> > near-ludicrous, theoretical-Kobayashi-Maru-sounding scenario.
> >
> > Cheers,
> >
> > Peter
> >
> > -----Original Message-----
> > From: javascript-bounces at LaTech.edu
> > [mailto:javascript-bounces at LaTech.edu] On Behalf Of Chris Tifer
> >
> > ----- Original Message ----- 
> > From: "Andrew Gibson" <andyg at ihug.co.nz>
> >
> > > Sorry im a bit late on this thread....from what I can gather you are
> > looking
> > > for a way to send and receive data from the server without the use
> of
> > POST,
> > > Get or Cookies?
> >
> > No, he's saying TO the server. The client is supposed to set some
> > Session Variable (a client-side cookie in actuality) on the server.
> >
> > _______________________________________________
> > Javascript mailing list
> > Javascript at LaTech.edu
> > https://lists.LaTech.edu/mailman/listinfo/javascript
> _______________________________________________
> Javascript mailing list
> Javascript at LaTech.edu
> https://lists.LaTech.edu/mailman/listinfo/javascript
>
>
> _______________________________________________
> Javascript mailing list
> Javascript at LaTech.edu
> https://lists.LaTech.edu/mailman/listinfo/javascript



More information about the Javascript mailing list