Other Available Downloads
Jun 3, 2015
Version 3.1 Highlights
- Device detection algorithm is over 100 times faster. Regular expressions and levenshtein distance calculations are no longer used.
- The device detection algorithm performance is no longer limited by the number of device combinations contained in the dataset.
- Two modes of operation are available:
- Memory – the detection data set is loaded into memory and there is no continuous connection to the source data file. Slower initialisation time but faster detection performance.
- Stream – relevant parts of the data set are loaded into memory when required and cached to improve performance. Rapid initialisation time but approximately 50% slower detection performance. This mode is used when operated in a web environment.
- Multi-threading is no longer used within the matching algorithm.
- When used in a web environment the detection results are stored within the session when available and are no longer cached separately.
- JPG and PNG format images can be optimised to improve performance.
- Bandwidth and response times can be monitored to understand in real time the end users experience.
- Feature detection is used to override properties in the data set to provide details such as iPhone model or the screen orientation. These values become available to the server from the 2nd request from the device onwards.
- Versions of .NET prior to 3.5 are no longer supported.
Changes between version 18.104.22.168
- Modified TopDevices.cs in the Web UI namespace so that duplicated devices within the same HardwareFamily are removed. This results in a nicer looking user interface when multiple models in the same family are present.
- Fixed Source.Dispose throwing an exception if a temporary data file could not be deleted. This should result in less temporary files being created.
- When working in Stream mode the temporary file must be present for the data set to be created. This addresses a rare situation where after the temporary file is checked but before the data set is created another process could delete the temporary file resulting in a Lite data set being created.
- WebProvider has been modified to augment Request.Browser with 3 additional pieces of information: MatchMethod, MatchDifference and MatchSignatureRank. All 3 can be used to check the level of confidence of the detector. I.e. when MatchMethod contains ‘exact’ the detector is confident that the user agent string in question corresponds to the matched device. If on the other hand the MatchMethod contains ‘none’ then the user agent is most certainly fake. For more information on all match methods please see: https://51degrees.com/support/documentation/pattern
- Added the response text from the server to the error log when a data file update fails. This can help provide more information about why automatic updates have failed.
- Results where Device-Stock-UA, X-Device-User-Agent or X-OperaMini-Phone-UA are present no longer generate an exception when interrogating signature rank.
No reviews yet for this release.
Opera does not support ClickOnce X
To install this application, save it and then open it. Opening it directly from Opera will not work correctly.