[Mono-bugs] [Bug 54133][Wis] Changed - Thread.Abort is not implemented on windows.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sat, 15 May 2004 08:50:41 -0400 (EDT)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by patrik.torstensson@intel.com.


--- shadow/54133	2004-05-13 15:25:02.000000000 -0400
+++ shadow/54133.tmp.18615	2004-05-15 08:50:41.000000000 -0400
@@ -3,13 +3,13 @@
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: NEW   
 Severity: Unknown
-Priority: Major
+Priority: Wishlist
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: liyul@hotmail.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -202,6 +202,17 @@
 ------- Additional Comments From liyul@hotmail.com  2004-02-11 20:39 -------
 Thank you for let me know the Response.End could be using
 thread.Abort. Actually Response.Redirect seemed to trigger the bug,
 too. The xsp authtest\index.aspx failed with same sympton under
 windows. There should be ways of fixing it without using thread.Abort,
 though that may require changing the StateMachine.
+------- Additional Comments From Patrik.Torstensson@intel.com  2004-05-15 08:50 -------
+Response.Redirect does a Response.End, this to make sure that code 
+that currently executing get's the possibility to clean up before 
+doing the redirect. There is no-way to change this, not if we going 
+to keep us working the same way as ms.
+Thread.abort is not implemented on windows and is not easy to 
+implement until we have changed the way how abort works, maybe not 
+even will it be possible. MS handles abort internally in a total 
+different way.