Release Candidate 11 for 1.3.0

• Fixed schema version configuration. Defaults to the schema version of the Devices.xml file but can be overridden by the SchemaVersion in the cfg file.
• Fixed generation of AssetRemoved when operating in version 1.2.
• Added Conversion Required to suppress units conversion on a per adapter or per agent basis.

Release Candidate 10 for 1.3.0

• Added support for Asset remove from HTTP and adapter feeds.
• Added filtering of removed assets per 1.3 changes.
• Added additional Asset tests.
• Added top level asset node parsing.
• Added count parameter per 1.3.
• Added better support for extended assets.

Release Candidate 9 for 1.3.0

• Added MIME type to correctly set the content-type for static files.

Release Candidate 8 for 1.3.0

• Updated documentation.
• Fixed line in XSD schema file
• Fixed static file handling in windows – treat all files as binary.

Release Candidate 7 for 1.3.0

• Added style sheets to the agent to have the XML formatted when used from a browser.
  • Adds one processing instruction when enabled. Sample streams styles included.
• Updated documentation
• Sample argument count now specifies the max number of results, not the window.

Release Candidate 6 for 1.3.0

• Fixed extra Z at end of create time in XML headers
• Fixed configuration test to include assets schema
• Updated tests to use 1.3 schemas.

Release Candidate 5 for 1.3.0

• Fixed * PONG response with single trailing space or malformed frequency.
• Fixed Date: header when streaming in Windows – now correct RFC 822 format
• Windows now uses FILETIME to get microsecond resolutions
• Fixed atomic increment on OS X – using new interfaces in 10.9

Release Candidate 4 for 1.3.0

• Xcode 5.0 10.9 compatibility.
• Max heartbeat timeout is 30 minutes
• Fixed schema location with secondary namespace
• Added 1.3 asset extensibility with support for xs:any with tests

Version 1.2.0.23

• Changed maximum heartbeat timeout to 30 minutes (used to be 2 minutes).

Version 1.2.0.22

• Fixed inclusion of extended schema along with the MTConnect schemas. Now schema location is set correctly.