User Tools

Site Tools


drivity_tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
drivity_tools [2014/03/08 20:57]
aznamerovsky
drivity_tools [2014/03/08 20:59]
aznamerovsky
Line 42: Line 42:
  
 The high level interface is to provide the unified approach for most common things and simplify access to the useful, but complicated features. In case of more special tasks, the programmer should use lower level Drivity Tools interfaces. The high level interface is to provide the unified approach for most common things and simplify access to the useful, but complicated features. In case of more special tasks, the programmer should use lower level Drivity Tools interfaces.
 +
 +
 +==== COMPARISON WITH OTHER APPROACHES ​ ====
 +
 +
 +**SSL**
 +
 +Drivity Tools security approach is very similar to SSL. It also uses symmetrical data encryption with asymmetrical encryption of session key and has a comparable level of protection. The key difference Drivity Tools has no extra functions, it uses just one crypto hash algorithm (SHA1), one symmetrical encryption approach (AES256) and one asymmetrical algorithm (RSA). It also doesn'​t include X.509 support and third party certificates validation, which is important for Internet communication,​ but typically unuseful for autonomous vehicle tracking with pre-programmed keys.
 +
 +**gpsd**
 +
 +Drivity tools contains only one parser for regular text NMEA. It doesn'​t support proprietary GPS receiver formats as well as binary NMEA. Drivity Tools is not to be used as a universal GPS processing software, but as an easy processor for most common data format, supported by the most of receivers.
  
drivity_tools.txt ยท Last modified: 2014/03/08 21:02 by aznamerovsky