scaling web services and dynamic URL's.....

[Ollie]

okay before anyone says I shouldn't use session state in a web services
don't both.....

I have 2 web services that both use sesssion state and share the session
state between the web services, this is achieved by using out-of-process
session state using MS state server.

This all works perfectly fine when the 'URL behavior' is set to static, but
when the 'URL behavior' dynamic the session state is not being shared
between the web services as I expected it would be.

This leads me to believe that the session id is some how generated from the
dynamic URL that is read from the web.config, I guess what this means is
that 2 different web service's URL will get 2 completey different session
states in the MS state server. Is there anyway to make them share the same
session?

This then makes me wonder how are you meant to scale web services that use
session state or are you meant not?

Cheers

Ollie

[Jan Tielens]

I think you've already answered your last question:

This then makes me wonder how are you meant to scale web services that use
session state or are you meant not?
In the first scentence: okay before anyone says I shouldn't use session state in a web services
don't both.....
:-)

Sorry, I couldn't resist...

--
Greetz
Jan
____________________
Read my weblog: http://weblogs.asp.net/jan
"Ollie" <ol**********@hotmail.com> schreef in bericht
news:eZ*************@TK2MSFTNGP09.phx.gbl... okay before anyone says I shouldn't use session state in a web services
don't both.....

I have 2 web services that both use sesssion state and share the session
state between the web services, this is achieved by using out-of-process
session state using MS state server.

This all works perfectly fine when the 'URL behavior' is set to static, but when the 'URL behavior' dynamic the session state is not being shared
between the web services as I expected it would be.

This leads me to believe that the session id is some how generated from the dynamic URL that is read from the web.config, I guess what this means is
that 2 different web service's URL will get 2 completey different session
states in the MS state server. Is there anyway to make them share the same
session?

This then makes me wonder how are you meant to scale web services that use
session state or are you meant not?

Cheers

Ollie

[Ollie]

Cheers Jan :)

Changed it now to stateless cos I came to the same conclusion....
"Jan Tielens" <ja*@no.spam.please.leadit.be> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...

I think you've already answered your last question:

This then makes me wonder how are you meant to scale web services that use session state or are you meant not?

In the first scentence:

okay before anyone says I shouldn't use session state in a web services
don't both.....

:-)

Sorry, I couldn't resist...

--
Greetz
Jan
____________________
Read my weblog: http://weblogs.asp.net/jan
"Ollie" <ol**********@hotmail.com> schreef in bericht
news:eZ*************@TK2MSFTNGP09.phx.gbl...

okay before anyone says I shouldn't use session state in a web services
don't both.....

I have 2 web services that both use sesssion state and share the session
state between the web services, this is achieved by using out-of-process
session state using MS state server.

This all works perfectly fine when the 'URL behavior' is set to static,

but

when the 'URL behavior' dynamic the session state is not being shared
between the web services as I expected it would be.

This leads me to believe that the session id is some how generated from

the

dynamic URL that is read from the web.config, I guess what this means is
that 2 different web service's URL will get 2 completey different session states in the MS state server. Is there anyway to make them share the same session?

This then makes me wonder how are you meant to scale web services that use session state or are you meant not?

Cheers

Ollie