"Setting" a Cookie

[Don]

I understand that when I send a cookie in a client-side page containing JS, it isn't actually "set"
until the next page is loaded. Is there some way to "set" it within the same html/JS page so it can
be accessed by other JS scripts in the same page?

Thanks,
Don

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Evertjan.]

Don wrote on 13 feb 2005 in comp.lang.javascript:

I understand that when I send
You mean "set" I hope?
a cookie in a client-side page
containing JS, it isn't actually "set" until the next page is loaded.
Is there some way to "set" it within the same html/JS page so it can
be accessed by other JS scripts in the same page?

That would mean that if your first page is loaded and then you trip over
the power cable, disconnecting the pc, the cookie would not be set?

Seems very improbable to me.
--
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)

[Don]

On 13 Feb 2005 14:17:11 GMT, "Evertjan." <ex**************@interxnl.net> wrote:

Don wrote on 13 feb 2005 in comp.lang.javascript:

I understand that when I send

You mean "set" I hope?

a cookie in a client-side page
containing JS, it isn't actually "set" until the next page is loaded.
Is there some way to "set" it within the same html/JS page so it can
be accessed by other JS scripts in the same page?

That would mean that if your first page is loaded and then you trip over
the power cable, disconnecting the pc, the cookie would not be set?

Seems very improbable to me.

My tests seem to verify what I've read, and that is that the browser doesn't actually "set" the
cookie until it encounters a subsequent page requiring its use. So, I suspose your theory that it
wouldn't be set it the pc lost power would be true.

Putting that aside, and assuming the foregoing is true, I'm looking for a way to force the browser
to set it in the same page containing the JS statement that attempts to set it.

Thanks,
Don

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Evertjan.]

Don wrote on 13 feb 2005 in comp.lang.javascript:

That would mean that if your first page is loaded and then you trip
over the power cable, disconnecting the pc, the cookie would not be
set?

Seems very improbable to me. My tests seem to verify what I've read, and that is that the browser
doesn't actually "set" the cookie until it encounters a subsequent
page requiring its use.

How did you test that, Don?
So, I suspose your theory that it wouldn't be
set it the pc lost power would be true.
Well I don't, offhand.
Putting that aside, and assuming the foregoing is true,
I would not assume that.
Please tell me what you mean by "set" in this case:
That the cooky file is placed in the IE temp structure?

What if that 'next page' is accessed a month later and the browser has
been closed down inbetween. Would you suggest that the cookie [one with
an expiry date, I mean, of course] is lost then?

That is contrary to my experience.

If it is not lost and not set,
where would the information be kept during that month?
I'm looking
for a way to force the browser to set it in the same page containing
the JS statement that attempts to set it.

Not possible in my opinion, follows your wrong assumption.

=======================

Let's test it, however:
<script type='text/javascript'>

document.cookie="myName=Evertjan"

alert(document.cookie)

</script>

It seems I am right, Don,
it returns the cookie string the first time.
--
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)

[Don]

On 13 Feb 2005 15:05:49 GMT, "Evertjan." <ex**************@interxnl.net> wrote:

Don wrote on 13 feb 2005 in comp.lang.javascript:

That would mean that if your first page is loaded and then you trip
over the power cable, disconnecting the pc, the cookie would not be
set?

Seems very improbable to me.

My tests seem to verify what I've read, and that is that the browser
doesn't actually "set" the cookie until it encounters a subsequent
page requiring its use.

How did you test that, Don?

So, I suspose your theory that it wouldn't be
set it the pc lost power would be true.

Well I don't, offhand.

Putting that aside, and assuming the foregoing is true,

I would not assume that.
Please tell me what you mean by "set" in this case:
That the cooky file is placed in the IE temp structure?

What if that 'next page' is accessed a month later and the browser has
been closed down inbetween. Would you suggest that the cookie [one with
an expiry date, I mean, of course] is lost then?

That is contrary to my experience.

If it is not lost and not set,
where would the information be kept during that month?

I'm looking
for a way to force the browser to set it in the same page containing
the JS statement that attempts to set it.

Not possible in my opinion, follows your wrong assumption.

=======================

Let's test it, however:
<script type='text/javascript'>

document.cookie="myName=Evertjan"

alert(document.cookie)

</script>

It seems I am right, Don,
it returns the cookie string the first time.

Evertjan,

You're right. I just realized in my script I use a function to extract cookies, and I didn't
extract again after making a change. So, it didn't look like my change had taken effect. Can't
believe I missed that one. I must have misinterperted the passage about a cookie not being set
until the following page is read. I think what they probably meant was that it isn't set until the
next reference (which apparently can be in the same page).

Thanks for your help.
Don

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Lee]

Don said:

You're right. I just realized in my script I use a function to extract cookies,
and I didn't
extract again after making a change. So, it didn't look like my change had
taken effect. Can't
believe I missed that one. I must have misinterperted the passage about a
cookie not being set
until the following page is read. I think what they probably meant was that it
isn't set until the
next reference (which apparently can be in the same page).

As far as the current page is concerned, the value is set immediately.
Your reference is probably saying that the server doesn't see the value until
the next time the page is requested.

[Don]

On 13 Feb 2005 12:23:03 -0800, Lee <RE**************@cox.net> wrote:

Don said:

You're right. I just realized in my script I use a function to extract cookies,
and I didn't
extract again after making a change. So, it didn't look like my change had
taken effect. Can't
believe I missed that one. I must have misinterperted the passage about a
cookie not being set
until the following page is read. I think what they probably meant was that it
isn't set until the
next reference (which apparently can be in the same page).

As far as the current page is concerned, the value is set immediately.
Your reference is probably saying that the server doesn't see the value until
the next time the page is requested.

Ok, that makes more sense to me. Thanks for your reply.
Don

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Dr John Stockton]

JRS: In article <Xn********************@194.109.133.29>, dated Sun, 13
Feb 2005 14:17:11, seen in news:comp.lang.javascript, Evertjan.
<ex**************@interxnl.net> posted :

Don wrote on 13 feb 2005 in comp.lang.javascript:

I understand that when I send

You mean "set" I hope?

a cookie in a client-side page
containing JS, it isn't actually "set" until the next page is loaded.
Is there some way to "set" it within the same html/JS page so it can
be accessed by other JS scripts in the same page?

That would mean that if your first page is loaded and then you trip over
the power cable, disconnecting the pc, the cookie would not be set?

Seems very improbable to me.

ISTM quite possible that a browser reads the cookie file into memory
when it starts, uses the memory file for read/write, and saves the
cookie file when it is closed down. Other programs seem to work that
way with "status" information. One could test it by playing with
cookies in a two-browser system, or by viewing the cookie file by a non-
browser method, or by something like the method you imply (pressing the
reset button seems kinder).

Or that it only writes the cookie file on page change.

But I don't know whether it does either of those in this case.

--
© John Stockton, Surrey, UK. ?@merlyn.demon.co.uk DOS 3.3, 6.20; Win98. ©
Web <URL:http://www.merlyn.demon.co.uk/> - FAQqish topics, acronyms & links.
PAS EXE TXT ZIP via <URL:http://www.merlyn.demon.co.uk/programs/00index.htm>
My DOS <URL:http://www.merlyn.demon.co.uk/batfiles.htm> - also batprogs.htm.

[Randy Webb]

Evertjan. wrote:

<--snip-->

Let's test it, however:
<script type='text/javascript'>

document.cookie="myName=Evertjan"

alert(document.cookie)

</script>
That doesn't mean a cookie was set, it means either a cookie was set or
a property of document named cookie was set to myName=Evertjan. Test:

<script type='text/javascript'>
document.chicken="myName=Evertjan"
alert(document.chicken)
</script>
It seems I am right, Don,
I disagree.
it returns the cookie string the first time.

No, it returns a property of document named cookie. It doesn't mean a
cookie was actually written, stored, or saved.

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly

[Evertjan.]

Randy Webb wrote on 14 feb 2005 in comp.lang.javascript:

No, it returns a property of document named cookie. It doesn't mean a
cookie was actually written, stored, or saved.

That was why I repeatedly asked for a definition of "set".

Your above de facto definition of a cookie-with expiry date
is not my interpretation of "set" in the context of the OQ,
as all he wanted is to use the cookie content on the same page,
as I believe. Not in a dual browser setup.

That such cookies are not saved even if the browser is not closed when the
pc craches or looses power before that seems out of the question, but you
could proove that by testing in the way you suggested.

--
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)