diff options
author | Justin Clark-Casey (justincc) | 2013-05-01 19:01:43 +0100 |
---|---|---|
committer | Justin Clark-Casey (justincc) | 2013-05-01 19:01:43 +0100 |
commit | 206fb306a7820cf593570e35ddfa8e7c5a10e449 (patch) | |
tree | 0ef0fdf42ddc0b63224af52b62b0bad42f62e352 /ThirdParty/SmartThreadPool/AssemblyInfo.cs | |
parent | Fix CAPS to work like they should - do not send caps to the viewer if they're... (diff) | |
download | opensim-SC_OLD-206fb306a7820cf593570e35ddfa8e7c5a10e449.zip opensim-SC_OLD-206fb306a7820cf593570e35ddfa8e7c5a10e449.tar.gz opensim-SC_OLD-206fb306a7820cf593570e35ddfa8e7c5a10e449.tar.bz2 opensim-SC_OLD-206fb306a7820cf593570e35ddfa8e7c5a10e449.tar.xz |
Update SmartThreadPool to latest version 2.2.3 with a major and minor change.
SmartThreadPool code comes from http://www.codeproject.com/Articles/7933/Smart-Thread-Pool
This version implements thread abort (via WorkItem.Cancel(true)), threadpool naming, max thread stack, etc. so we no longer need to manually patch those.
However, two changes have been made to stock 2.2.3.
Major change: WorkItem.Cancel(bool abortExecution) in our version does not succeed if the work item was in progress and thread abort was not specified.
This is to match previous behaviour where we handle co-operative termination via another mechanism rather than checking WorkItem.IsCanceled.
Minor change: Did not add STP's StopWatch implementation as this is only used WinCE and Silverlight and causes a build clash with System.Diagnostics.StopWatch
The reason for updating is to see if this improves http://opensimulator.org/mantis/view.php?id=6557 and http://opensimulator.org/mantis/view.php?id=6586
Diffstat (limited to '')
-rw-r--r-- | ThirdParty/SmartThreadPool/AssemblyInfo.cs | 61 |
1 files changed, 0 insertions, 61 deletions
diff --git a/ThirdParty/SmartThreadPool/AssemblyInfo.cs b/ThirdParty/SmartThreadPool/AssemblyInfo.cs deleted file mode 100644 index e2465b0..0000000 --- a/ThirdParty/SmartThreadPool/AssemblyInfo.cs +++ /dev/null | |||
@@ -1,61 +0,0 @@ | |||
1 | using System; | ||
2 | using System.Reflection; | ||
3 | using System.Runtime.InteropServices; | ||
4 | |||
5 | // | ||
6 | // General Information about an assembly is controlled through the following | ||
7 | // set of attributes. Change these attribute values to modify the information | ||
8 | // associated with an assembly. | ||
9 | // | ||
10 | [assembly: AssemblyTitle("")] | ||
11 | [assembly: AssemblyDescription("")] | ||
12 | [assembly: AssemblyConfiguration("")] | ||
13 | [assembly: AssemblyCompany("")] | ||
14 | [assembly: AssemblyProduct("")] | ||
15 | [assembly: AssemblyCopyright("")] | ||
16 | [assembly: AssemblyTrademark("")] | ||
17 | [assembly: AssemblyCulture("")] | ||
18 | [assembly: ComVisible(false)] | ||
19 | [assembly: CLSCompliant(true)] | ||
20 | |||
21 | // | ||
22 | // Version information for an assembly consists of the following four values: | ||
23 | // | ||
24 | // Major Version | ||
25 | // Minor Version | ||
26 | // Build Number | ||
27 | // Revision | ||
28 | // | ||
29 | // You can specify all the values or you can default the Revision and Build Numbers | ||
30 | // by using the '*' as shown below: | ||
31 | |||
32 | [assembly: AssemblyVersion("0.7.6.*")] | ||
33 | |||
34 | // | ||
35 | // In order to sign your assembly you must specify a key to use. Refer to the | ||
36 | // Microsoft .NET Framework documentation for more information on assembly signing. | ||
37 | // | ||
38 | // Use the attributes below to control which key is used for signing. | ||
39 | // | ||
40 | // Notes: | ||
41 | // (*) If no key is specified, the assembly is not signed. | ||
42 | // (*) KeyName refers to a key that has been installed in the Crypto Service | ||
43 | // Provider (CSP) on your machine. KeyFile refers to a file which contains | ||
44 | // a key. | ||
45 | // (*) If the KeyFile and the KeyName values are both specified, the | ||
46 | // following processing occurs: | ||
47 | // (1) If the KeyName can be found in the CSP, that key is used. | ||
48 | // (2) If the KeyName does not exist and the KeyFile does exist, the key | ||
49 | // in the KeyFile is installed into the CSP and used. | ||
50 | // (*) In order to create a KeyFile, you can use the sn.exe (Strong Name) utility. | ||
51 | // When specifying the KeyFile, the location of the KeyFile should be | ||
52 | // relative to the project output directory which is | ||
53 | // %Project Directory%\obj\<configuration>. For example, if your KeyFile is | ||
54 | // located in the project directory, you would specify the AssemblyKeyFile | ||
55 | // attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")] | ||
56 | // (*) Delay Signing is an advanced option - see the Microsoft .NET Framework | ||
57 | // documentation for more information on this. | ||
58 | // | ||
59 | [assembly: AssemblyDelaySign(false)] | ||
60 | [assembly: AssemblyKeyFile("")] | ||
61 | [assembly: AssemblyKeyName("")] | ||