Hi Marcin, >> Yep, this is exactly what I had in mind. The problem though is that >> somebody still needs to pass in that callback. So maybe we could >> change gatt_db_read to accept an additional callback/user_data which >> would then get forwarded to the registered gatt_db_read_t. That would >> definitely fix the problem here. It would also not break the android >> code, since it can already work without invoking the callback. I'll >> experiment with this. > > I thought about simple callout, like gatt_db_result().Gatt_db can call > read callback with > specific data, like gatt_db_transaction_data, then, once app, server > or anything will complete > read or write operation, just simply call gatt_db_result() with > previously passed transaction data. > That makes sense. For now, I'm leaving the callback out of the first patch set. I'll think about this a little more and upload something later this week. Thanks, Arman -- 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
