On Mon, Apr 08, 2013 at 11:16:07AM -0700, Tejun Heo wrote: > > Given the fact that library has view of full system resoruces (both > > persistent view and active view), shouldn't we just be able to extend > > the API to meet additional configuration or resource needs. > > Maybe, I don't know. It just looks like a weird approach to me. > Wouldn't it make more sense to implement it as a dbus service that > everyone talks to? That's how our base system is structured these > days. Why should this be any different?
To expand a bit, the base system being composed that way makes a lot of sense. It becomes clear who's responsible for what and there's a reliable way to recover when things go awry on the clients' sides. Also, it pretty much *forces* you to design an interface which fits the problem domain properly rather than exposing all the control knobs there are without thinking how they'd be actually useful. The language binding issue is much easier too - it's already solved. It seems like the only logical thing to do, well, at least to me. Am I missing something? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
