On 23/09/10 22:25, Greg KH wrote:
On Thu, Sep 23, 2010 at 10:45:45PM +0200, Thiago Macieira wrote:
On Thursday 23. September 2010 21.05.56 Greg KH wrote:
I don't see ConnMan providing an API or ABI, do you? If so, where is it
documented?
Yes, I do. It has a D-Bus API.
So, if _thats_ the requirement, then document that, not "you must use
connman".
Hmmm
Seems that one solution would be that people wishing to see an interface for an
area (eg for the purpose of abstracting out a selected component) could propose
and get agreement to documentation for it?
Obviously if the new component's API is as well documented as ConnMan's clearly
should be but isnt'... and assuming it is compatible, then donating that
documentation would be a great first step.
The problem of course arises when "undocumented APIs" are used; even such things
as writing to a MeeGo config file (which may == a ConnMan config file at the
moment if it has any).
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
