I think the most "dangerous" behaviour in this matter is that you may
prematurely end a cleanup algorithum in the middle. This is especially
important if you're using unsafe components that should explicitly call
cleanup yourself.
Actually, I always use Response.Redirect() so this is not a problem with me.
(The overhead to initiate another request is not considered a big problem
here.)
"Guadala Harry" <GMan@NoSpam.com> 秎ン
news:uEVThLTrEHA.756@TK2MSFTNGP11.phx.gbl い级糶...[color=blue]
> The articles you provided are exactly the ones that inspired my post! The
> first one is the one that explicitly states that one should NOT use
> Server.Transfer and instead use Server.Execute as a workaround for "this
> problem" which is also "by design".... Thus my initial confusion. We have[/color]
a[color=blue]
> situation that is created by design: I clearly understand *why*
> ThreadAbortException is raised. I clearly understand that I have[/color]
alternative[color=blue]
> ways to transfer users around my application. What I'm still not sure of[/color]
is[color=blue]
> the extent to which Server.Transfer is dangerous (or not). In the second
> link you provided (thank you - I should have provided those in my OP), the
> author states about ending a response, "This is a very violent thing to[/color]
do."[color=blue]
> Very violent? I'll buy it - this guy seems to know his stuff and is
> apparently a credible source. So, I'm wondering, if it is in fact, "very
> violent," then should I ever knowingly let it happen in my application? I
> think the obvious ansers is "of course you should never knowingly let a[/color]
very[color=blue]
> violent thing happen" in your application. The implication is that one
> should, then, *never* user Server.Transfer because it *always* results in
> the original response being terminated (which is a "very violent" thing).
>
> Perhaps I'm just being overly cautious here (okay, paranoid). I'd really
> like to know because I really like the idea of being able to use
> Server.Transfer. I'm just rather uncomfortable ThreadAbortException
> knowingly occuring. Is ThreadAbortException really not hurting anything;[/color]
and[color=blue]
> I would be perfectly responsible to let it happen as a matter of routine[/color]
in[color=blue]
> a busy application? I'd really like to know as Server.Transfer is[/color]
otherwise[color=blue]
> a godsend in certain situations. Thanks!
>
> The fact that you're paranoid doesn't mean you're not being followed!
>
> GH
>
>
>
>
> "Lau Lei Cheong" <leu_lc@yehoo.com.hk> wrote in message
> news:ONusKoRrEHA.1164@TK2MSFTNGP10.phx.gbl...[color=green]
> > You may find relevent information here.
> >
http://support.microsoft.com/default...b;EN-US;312629
> >
http://blogs.msdn.com/bleroy/archive...03/207486.aspx
> >
> > "Guadala Harry" <GMan@NoSpam.com> 秎ン
> > news:enxahBOrEHA.1296@TK2MSFTNGP12.phx.gbl い级糶...[color=darkred]
> > > I've been reading up on Server.Transfer as well as doing some testing,[/color][/color]
> and[color=green][color=darkred]
> > > it appears to always raise the ThreadAbortException error. On one hand[/color]
> > I've[color=darkred]
> > > read a bunch of promotional-type material touting the benefits of
> > > Server.Transfer and none of them mention ThreadAbortException - but[/color][/color][/color]
the[color=blue][color=green]
> > MSDN[color=darkred]
> > > documentation says Server.Transfer will always cause that exception -[/color][/color][/color]
by[color=blue][color=green][color=darkred]
> > > design - and that the work-around is to not use Server.Transfer (and[/color][/color][/color]
to[color=blue][color=green]
> > use[color=darkred]
> > > Server.Execute instead). Surprising indeed. "Here's a great new tool -[/color][/color]
> now[color=green][color=darkred]
> > > don't use it" is what I'm hearing from Microsoft about[/color][/color][/color]
Server.Transfer.[color=blue][color=green]
> > This[color=darkred]
> > > is confusing to me. Am I just missing something? Is[/color][/color][/color]
ThreadAbortException[color=blue][color=green][color=darkred]
> > > really not all that bad? I've read elsewhere that it really is bad and[/color][/color]
> to[color=green][color=darkred]
> > > avoid it at all costs.
> > >
> > > I'd appreciate it if anyone could clarify whether Server.Transfer is[/color][/color]
> okay[color=green]
> > to[color=darkred]
> > > use even though it always causes a ThreadAbortException.
> > >
> > > Thanks!
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]
