Integrate with another service

[nvandoorn]

This service never stores or publishes any data on it's own, it simply watches, records, and then waits for another service to do something with these values. This means we need to be mindful of the API we provide from this service. Additionally, we need to think about when it's available, and how quickly it must respond.

#3 specifies that we must capture all sudden impacts, so it may be a good idea to store a list of impact values in this service. brnkl_motion_getSuddenImpact currently transfers a single set of readings, but could be modified to transfer an array.

[nvandoorn]

Something I forgot to mention in the initial spec: brnkl_motion_getSuddenImpact should "flush out" the list of values stored in the motion service. The values have been transferred to where they will be published, so they are no longer required locally.