-
Notifications
You must be signed in to change notification settings - Fork 68
Home
Shinjiro Urata edited this page Feb 9, 2016
·
5 revisions
Welcome to the automotive wiki!
- API style
| Choices | Pros | Cons |
| subscribe() style (Current style) |
- Posible to disable by 'unsubscribe'. - Can save CPU, memory consumption? |
- 'Subscribe' is not common style. No good reputation for developers. |
| onchange, ondata style (Suggested from Generic Sensor API) |
- Common style. Developers are familiar to this. | - No way to unsubscribe? (or just set onchange = null and then garbagecollected?) - Only one callback function can be added? |
- Interface grouping (encapsulation)
| Choices | Pros | Cons |
| Current style (e.g. Fuel.subscribe()) |
- Possible to get group of values by one get()/subscribe(). - Easy to use when only coarse values are needed. |
- Not possible to get()/subscibe() by only one attribute. - Not possible to set different interval/threshold to attributes |
| Separated style. (e.g. something like Fuel.level.subscirbe()) |
- Possible to get()/subscribe() by only one attribute. - Possible to set different interval/threshold to each attribute |
- Need to set get()/subscribe() for each attributes one by one. |
- Constructor or not
| Choices | Pros | Cons |
| Current style (e.g. navigator.vehicle.door.subscribe()) |
- Simple and at least usable. | - Not modern. Not flexible. - Global name space pollution? |
| Using Constructor (e.g. var door = new Vehicle.Door() ) |
- Modern style. - Flexible to use. |
- Memory consumption? |
- Other topics
| Choices | Pros | Cons |
| - | - | |
| - | - |