How does a web service distinguish session states?

[Ken Varn]

In looking into Web Services, I noticed that they can maintain Session
variables. How does a web service distinguish different sessions? Does
this occur when the client creates an instance of the proxy class? If so,
then I am assuming that the client should create an instance of the service
proxy class for the lifetime that the client needs the web service. Is this
true?

Just a suggestion, but it seems like session variable management would be
much easier by just marking class fields with a SessionAttribute (or
something similar) if such an animal exists.

--
-----------------------------------
Ken Varn
Senior Software Engineer
Diebold Inc.

EmailID = varnk
Domain = Diebold.com
-----------------------------------

[Tomas Restrepo \(MVP\)]

Hi Ken,

In looking into Web Services, I noticed that they can maintain Session
variables. How does a web service distinguish different sessions?

On ASP.NET? The same way it does for ASP.NET webpages... cookies!

The rest of the mechanism works pretty much (both on the server and client
side) as the rest of the ASP.NET session mechanics. One thing to remember is
that, by default, the proxy classes generated won't have a cookie container
associated with them, and those won't be able to "remember" the session, so
you need to add that last part yourself if you want to enable it...

--
Tomas Restrepo
to****@mvps.org

[Ken Varn]

Thanks for your reply. If you don't mind, I have a few other questions
regarding session state.

In general, are ASP.NET sessions separated by workstation or by browser
connections? I basically want to know whether an object that I store in a
session variable will be available on the next call to the web service. In
other words, when does the session state go away?

Regarding your statement...

One thing to remember is
that, by default, the proxy classes generated won't have a cookie container associated with them, and those won't be able to "remember" the session, so you need to add that last part yourself if you want to enable it...
What do you mean by "remember" the session, and what "last part" are you
referring to?

--
-----------------------------------
Ken Varn
Senior Software Engineer
Diebold Inc.

EmailID = varnk
Domain = Diebold.com
-----------------------------------
"Tomas Restrepo (MVP)" <to****@mvps.org> wrote in message
news:uG**************@TK2MSFTNGP11.phx.gbl... Hi Ken,

In looking into Web Services, I noticed that they can maintain Session
variables. How does a web service distinguish different sessions?
On ASP.NET? The same way it does for ASP.NET webpages... cookies!

The rest of the mechanism works pretty much (both on the server and client
side) as the rest of the ASP.NET session mechanics. One thing to remember

is that, by default, the proxy classes generated won't have a cookie container associated with them, and those won't be able to "remember" the session, so you need to add that last part yourself if you want to enable it...

--
Tomas Restrepo
to****@mvps.org

[Tomas Restrepo \(MVP\)]

Hi ken,

Thanks for your reply. If you don't mind, I have a few other questions
regarding session state.

In general, are ASP.NET sessions separated by workstation or by browser
connections? I basically want to know whether an object that I store in a
session variable will be available on the next call to the web service. In other words, when does the session state go away?

When exactly depends on a lot of factors, like the kind of session store you
use, etc. Normally, sessions might have an expiration time, which under
normal conditions should be the controlling factor.

--
Tomas Restrepo
to****@mvps.org