Well I gather, that after code has executing on the server, the page is
going back to the client. The page has a header, and the cookie is
contained in that http header. Then the browser decides to save it, or
whatever. We use cookies all over the place, writing them, reading them,
normally we don't need to start up a separate browser session. The problem
here is that we wanted a cookie to write the machinename -- AND, we do not
have netbios on the desktops, so we can only get that machine name from an
app variable.
An app variable is available at startup (starting up the computer) that
contains this computer name, and thats the only place we figured we can get
this cookie written -- way before the user has even opened the application.
So we were going to open the app silently (hidden) during startup, write the
cookie, and then close the app.
Then when the user goes into the app later on, the cookie is there and we
can read it. But we found another solution. It turns out though, that we
found that the %COMPUTERNAME% app variable is always avail. on the user's
machine, even after startup, and it can be used in the querystring. So
we're able to call the app like:
http://myapp/default.aspx?computername=%COMPUTERNAME%
And i've got it working this way.... jason shohet
When they leave the server, they appear simply as a HTTP Header, like this:
Set-Cookie: NAME=VALUE; expires=DATE; path=PATH; domain=DOMAIN_NAME; secure
The browser then decides what to do with that text (if anything). Cookies
are also sent back to the server in the same manner.
Therefore, causing the page to Sleep will do absolutely nothing. Please
provide more specific infomation.
