Hi, On Thu, Jun 30, 2011 at 2:48 PM, Claudio Takahasi <claudio.takahasi@xxxxxxxxxxxxx> wrote: > On Wed, Jun 29, 2011 at 8:50 PM, <ingas@xxxxxxxxxxxxxx> wrote: >> I ran into a similar problem. Cannot we just delay the return of >> DiscoverCharacteristics method call until after the characteristic >> values/properties have been acquired? I tried out this solution and it >> seems to work fine. The trick is to implement internal counter for >> received responses from the remote device + timeout that is reset on each >> successful response. Any thoughts on this? > > IMO delay the return of DiscoverCharacteristics method is the most > simple solution. What about the D-Bus timeout (small) versus GATT timeout (30 seconds) ? We should avoid getting those "org.freedesktop.DBus.Error.NoReply: Did not receive a reply." errors. 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
