Vehicle Information API Draft : Filtering on subscribe to keep performance

Hello All

In our last f2f meeting in SF we quickly discussed to add  in the 
subscribe function a parameter for introducing a filter (named hysteresis) 
..  The goal of this parameter is to  limit the number of notification to 
the callback function.  This parameter is very important if we want to 
keep system performance, 

For example, the  engineSpeed (RPM) attribute has a very wide range for 
values.  The RPM will be updated very often (perhaps  every 1 rpm), which 
will generate thousands of notification.    To avoid unreleavant 
notification, an application can set the hysteresis to given value, such 
1000.   An another Apps (diag. app. for example) can request  this filter 
to 100 (or no no filtering at all) for a better analysis.  Each 
application been free to set this value in accordance with his own 
requirements. 

Having in mind to keep performance, I strongly propose to add an optional 
parameter (or additional method) to set the hysteresis when we subscribe 
to an attribute.

I will also send in a separate mail my remarks about the domain for some 
attributes:  i found that some attributes may require a "decimal" (float) 
data type for enhancing the data precision.

Unfortunately , i won't be able to join the f2f this week.  i will try to 
particapte thursday afternoon by phone

................................................. 
Sinceres salutations/Kind regards 
Daniel Jutras
Continental Automotive Rambouillet France SAS 
Business Unit - Infotainment & Connectivity
6 rue Jean Moulin - BP65 
F-78512 Rambouillet 
Tel. : +33 (0)1.34.57.77.07
Fax. : +33 (0)1.34.57.78.22 
E-mail daniel.jutras@continental-corporation.com
http://www.continental-corporation.com 

Please consider your environmental responsibility before printing this 
e-mail