Server.Transfer and Load Balanced Environments

[Chris Bellini]

Greetings!

I would like to use Server.Transfer to redirect users to a given page,
while maintaining the state of form fields. This works fine on a single
server.

However, this will be deployed in a load balanced environment. I know
that Session variables and load balanced environments don't mix. Do I
have a cause for concern with Server.Transfer as well?

Thanks in advance.
Chris

[Anthony Jones]

"Chris Bellini" <ch************ *@spam.chrisbel lini.blows.comw rote in
message news:eH******** ******@TK2MSFTN GP03.phx.gbl...

Greetings!

I would like to use Server.Transfer to redirect users to a given page,
while maintaining the state of form fields. This works fine on a single
server.

However, this will be deployed in a load balanced environment. I know
that Session variables and load balanced environments don't mix. Do I
have a cause for concern with Server.Transfer as well?

Thanks in advance.
Chris

Server transfer will not transfer the request to another server even in a
load balanced system.

[Aaron Bertrand [SQL Server MVP]]

I haven't done extensive testing of this, but I am fairly certain that both
server.transfer and server.execute will stay on the same server. At least
that's the theory ... I'll repeat that I haven't done any thorough testing
of this. As with most things, if you have concerns it shouldn't take much
to set up a test.

A


"Chris Bellini" <ch************ *@spam.chrisbel lini.blows.comw rote in
message news:eH******** ******@TK2MSFTN GP03.phx.gbl...

Greetings!

I would like to use Server.Transfer to redirect users to a given page,
while maintaining the state of form fields. This works fine on a single
server.

However, this will be deployed in a load balanced environment. I know
that Session variables and load balanced environments don't mix. Do I
have a cause for concern with Server.Transfer as well?

Thanks in advance.
Chris

[Dave Anderson]

Aaron Bertrand [SQL Server MVP] wrote:

I haven't done extensive testing of this, but I am fairly
certain that both server.transfer and server.execute will
stay on the same server. At least that's the theory ...

They HAVE TO stay on the same server. They share a response stream (unlike
Response.Redire ct, which tells the browser to send a new request, and
subsequently does not share a response stream with the original request).

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

[Aaron Bertrand [SQL Server MVP]]

They HAVE TO stay on the same server. They share a response stream (unlike

Response.Redire ct, which tells the browser to send a new request, and
subsequently does not share a response stream with the original request).

Right, after I posted I thought about it a bit more, and of course
server.transfer/execute would not possibly be able to send anything back out
to the load balancer, because by definition they stay local.

[Chris Bellini]

Aaron Bertrand [SQL Server MVP] wrote:

>They HAVE TO stay on the same server. They share a response stream (unlike
Response.Redir ect, which tells the browser to send a new request, and
subsequently does not share a response stream with the original request).

Right, after I posted I thought about it a bit more, and of course
server.transfer/execute would not possibly be able to send anything back out
to the load balancer, because by definition they stay local.

So it's safe to say that shouldn't run into any issues of having
hidden form fields disappear on me after a call to Server.Transfer ?
Chris

[Dave Anderson]

Chris Bellini wrote:

So it's safe to say that shouldn't run into any issues of
having hidden form fields disappear on me after a call to
Server.Transfer ?

Hidden form fields are a client-side issue. The server only knows requests.

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

[Anthony Jones]

"Chris Bellini" <ch************ *@spam.chrisbel lini.blows.comw rote in
message news:u3******** ******@TK2MSFTN GP03.phx.gbl...

Aaron Bertrand [SQL Server MVP] wrote:

They HAVE TO stay on the same server. They share a response stream

(unlike

Response.Redire ct, which tells the browser to send a new request, and
subsequently does not share a response stream with the original

request).

Right, after I posted I thought about it a bit more, and of course
server.transfer/execute would not possibly be able to send anything back

out

to the load balancer, because by definition they stay local.

So it's safe to say that shouldn't run into any issues of having
hidden form fields disappear on me after a call to Server.Transfer ?

No you shouldn't. All form fields will appear to the transfered to page the
same as they would have to the original target.

>
Chris

[Chris Bellini]

Anthony Jones wrote:

No you shouldn't. All form fields will appear to the transfered to page the
same as they would have to the original target.

>Chris

Phew, that's good to hear :) Thanks.
Chris

[Dave Anderson]

Anthony Jones wrote:

>So it's safe to say that shouldn't run into any issues of
having hidden form fields disappear on me after a call to
Server.Transfe r?

No you shouldn't. All form fields will appear to the
transfered to page the same as they would have to the
original target.

That's not technically correct. The two scripts share Request and Response
objects, which are server-side, while form fields (hidden or otherwise) are
client-side constructs.

The conclusion is correct, however. There should be no loss of Request
elements in the transfer from one script to another.

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.