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
Next revision Both sides next revision
drivity_tools [2014/03/08 20:53]
aznamerovsky
drivity_tools [2014/03/08 20:57]
aznamerovsky
Line 17: Line 17:
  
  
-Drivity Tools is available under GPL license due to using of internal components published under this license. You must put Drivity-based code to OSS domain by default. If you intend to use your code under some other conditions, please request Componentality for appropriate permit and legal assistance.+**Drivity Tools is available under GPL license** due to using of internal components published under this license. You must put Drivity-based code to OSS domain by default. If you intend to use your code under some other conditions, please request Componentality for appropriate permit and legal assistance.
  
 Copyright (c) 2014, Componentality Oy, Konstantin A. Khait Copyright (c) 2014, Componentality Oy, Konstantin A. Khait
Line 24: Line 24:
  
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 +
 +
 +==== WHAT DRIVITY TOOLS CONSISTS OF?  ====
 +
 +
 +Drivity Tools component contains several parts doing separated things and being integrated to a single entity just to avoid putting extra integration job to the programmer using it.
 +
 +**- Restricted edition of CST middleware.** Old, but still used set of components doing commonly used things like memory management and unified API provisioning. This framework is fully hidden from the applied level and shouldn'​t be accessed directly. CommonLibs code base becomes a replacement of CST middleware for Drivity Tools, but not yet completed
 +
 +**- Streaming NMEA parser.** This component is standalone and can be separated from entire Drivity Tools set if required for the project. NMEA parser can be used as very light and controllable replacement for gpsd and also applied for in-app tasks related to GPS data processing. It uses C++ API, which is event-based and might be a little bit sophisticated for simple tasks
 +
 +**- drvloc API.** Simplified non-streaming oriented API for vehicle location information management. Assumes packaging of the data to simple structures. Also contains primitive encryption API to cover easy security tasks. drvloc API is fully done in C, therefore can be precompiled to pure C projects.
 +
 +**- LBSAPI.** Full-scale tracking API, including data gathering, packaging to JSON structures, encryption and decryption, keys management and so on. Might be used for complex tracking projects.
 +
 +**- drivity CLI** - command line utility for most typical operations.
 +
 +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.