Justin Clark-Casey (justincc) 89efccaa71 Rather than instantiating a UTF8 encoding everywhere when we want to supress the BOM, use a single Util.UTF8NoBomEncoding. ... This class is thread-safe (as evidenced by the provision of the system-wide Encoding.UTF8 which does not suppress BOM on output).		2012-07-19 00:57:36 +01:00
..
ApplicationPlugins	Don't include time to transmit response back to requester when assessing slow handling of requests.	2012-06-20 23:29:49 +01:00
Capabilities	Rather than instantiating a UTF8 encoding everywhere when we want to supress the BOM, use a single Util.UTF8NoBomEncoding.	2012-07-19 00:57:36 +01:00
ConsoleClient	Where possible, use the system Encoding.ASCII and Encoding.UTF8 rather than constructing fresh copies.	2012-07-19 00:25:40 +01:00
Data	minor: remove some recent mono compiler warnings	2012-07-11 23:07:17 +01:00
Framework	Rather than instantiating a UTF8 encoding everywhere when we want to supress the BOM, use a single Util.UTF8NoBomEncoding.	2012-07-19 00:57:36 +01:00
Region	Rather than instantiating a UTF8 encoding everywhere when we want to supress the BOM, use a single Util.UTF8NoBomEncoding.	2012-07-19 00:57:36 +01:00
Server	Rather than instantiating a UTF8 encoding everywhere when we want to supress the BOM, use a single Util.UTF8NoBomEncoding.	2012-07-19 00:57:36 +01:00
Services	Rather than instantiating a UTF8 encoding everywhere when we want to supress the BOM, use a single Util.UTF8NoBomEncoding.	2012-07-19 00:57:36 +01:00
Tests	Remove IClientAPI.GetClientEP() in favour of existing identical IClientAPI.RemoteEndpoint.	2012-07-19 00:45:02 +01:00
Tools	Where possible, use the system Encoding.ASCII and Encoding.UTF8 rather than constructing fresh copies.	2012-07-19 00:25:40 +01:00