search

callmebac / funf-open-sensing-framework

Automatically exported from code.google.com/p/funf-open-sensing-framework
0 stars 0 forks source link

Add triggers #71

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Probes are currently only run on schedules.  We want to be able to run them 
when events occur, instead of on independent schedules.  

As an example, imagine we wanted to scan a persons location everytime the 
WifiProbe scanned.  In the configuration we would specify in data requests:

"edu.mit.media.funf.probe.builtin.WifiProbe": [
    { "PERIOD": 300 }
],
"edu.mit.media.funf.probe.builtin.LocationProbe": [
    { "TRIGGER": "edu.mit.media.funf.probe.builtin.WifiProbe"}
]

This would ensure we have a location point very close in time to the wifi scan 
point.

To implement this, each probe will have the option to support the "TRIGGER" 
parameter.  If it supports the parameter, it will send a PASSIVE ONLY data 
request to the probe name specified by the parameter.  When it receives a data 
request from this probe it will also run.  

In order to dynamically decide whether or not the probe runs, the developer may 
implement their own custom probe or they can introduce an intermediary trigger 
probe that will relay the information in certain cases, but not in others.

Original issue reported on code.google.com by alan.gar...@gmail.com on 5 Dec 2011 at 9:52

GoogleCodeExporter commented 9 years ago 
Triggers could be probe names, or potentially broadcast actions.

Original comment by alan.gar...@gmail.com on 8 Dec 2011 at 4:12