Hi Arun, On Wed, May 16, 2012 at 7:40 AM, Arun K. Singh <arunkat@xxxxxxxxx> wrote: > Hi Anderson, > > On Thu, Feb 2, 2012 at 4:42 AM, Anderson Lizardo > <anderson.lizardo@xxxxxxxxxxxxx> wrote: > > <snip> > .. > >> But even with the initial implementation, most Time clients will be >> supported just fine. They will just not be able to update the phone's >> own time or be notified of manual changes to the phone time (this will >> be supported with the D-Bus API). > > Unless I missed such discussions on Time client support, could you > comment on plans to support it. From what I figure is a time client > will need to configure few things on the server such as notifying on > time udpates/reference time etc. which may need dedicated API's. Do > you have plans to support time client API's as well? The current code (and the relevant discussion) is only related to Time Server D-BUS API. It is needed so the platform specific stuff (e.g. system clock update) can be done outside of BlueZ, by a Time "agent". If you are interested on implementing Time Client support, you will need to propose a separate API. I am not aware of anyone working on client side support. > > Thanks, > Arun Best Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
