Idea for context defined profiles

[Michael 'Mickey' Lauer]

Steven,

thanks for contacting Guillaume, I already read your wiki page a when you 
added it and I think share a good amount of ideas there.

I think the first thing to think about is some use cases that give a rough 
idea about what we actually want from the context manager.

Then, we need to think about the context entity per se. contexts can be made 
of several data sources, e.g.

* time
* location [please think about if and how to include geoclue here]
* connection status, i.e. devices in vincinity [cooperate with intel 
connection manager or NM]
* ...

The API should support specifying a context as a number of parameters (not 
just simple parameters, but also e.g. an interval or a number of cell 
towers).
The API might support setting a context hint, so that the context manager can 
map the current context to a named context.

The API might feature a signal that is sent, when the device "enters" a named 
context again.

What happens on context changes should be the 2nd thing to think about. Of 
course, the first idea is automatic profile changes, which makes a lot of 
sense.

I think there's a huge potential for context sensitive applications in general 
and we might not see interesting use cases at once, but I'm 100% sure they 
will come.

-- 
Dr. Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de