[Javascript] Passing variables from one page to another

[john at jwarner.com (John Warner)]

> My apology for sloppy wording -- I think you knew what I meant.

I don't agree with you here. I seriously believe after spending a
paragraph or so on a topic that actually had nothing to do with the
problem at hand, that your wording error sailed completely over his
head. Otherwise why make an issue of clumsy phrasing which we are all
guilty of from time to time. No, you give the poster too much credit
with your reply here. Anytime a question such as yours devolves into a
discussion of statefulness, the poster has missed the point of the
question totally and is likely a newly minted (sp intentional) CS major
who has to show off that lecture from last semester.

John Warner


> -----Original Message-----
> From: javascript-bounces@xxxxxxxxxx 
> [mailto:javascript-bounces@xxxxxxxxxx] On Behalf Of tedd
> Sent: Thursday, December 28, 2006 9:18 AM
> To: [JavaScript List]
> Subject: Re: [Javascript] Passing variables from one page to another
> 
> 
> At 1:42 PM -0500 12/27/06, Matt Warden wrote:
> >On 12/27/06, tedd <tedd@xxxxxxxxxxxx> wrote:
> >>There are several ways that I can pass variables between 
> pages in php, 
> >>such as to use sessions or cookies, but those are required 
> because the 
> >>operations are server-side and thus stateless.
> >
> >There is nothing about server-side that makes it stateless. The 
> >interaction between client and server is what is stateless, 
> thus things 
> >are stateless from the perspective of the client as well (it must 
> >maintain state itself).
> 
> My apology for sloppy wording -- I think you knew what I meant.
> 
> The "operation" I'm addressing here is going from page to page (i.e., 
> interaction between client and server) which on the server-side is 
> stateless. I understand the server-side has to deal with different 
> requests coming from many different users at nearly the same time and 
> as such, it has to be stateless.
> 
> However, but I never considered client-side stateless because it's 
> client-side (I realize that I'm wrong, but just don't know why).
> 
> I thought that javascript being client-side and having to deal with 
> only one user might be different. After all, it is only one user 
> using one browser running javascript, right?
> 
> So, where's the problem with javascript keeping variables 
> alive between pages?
> 
> Thanks in advance for the upcoming education.
> 
> tedd