Re: [PATCH ] tools: Add unregister gatt service

[Johan Hedberg <johan.hedberg@gmail.com>]

Hi Bharat,

On Mon, Jul 21, 2014, Bharat Bhusan Panda wrote:
> > > +static int id;
> > > +
> > >  struct characteristic {
> > >  	char *uuid;
> > >  	char *path;
> > > @@ -332,10 +334,10 @@ static gboolean register_characteristic(const
> > > char *chr_uuid,
> > >
> > >  static char *register_service(const char *uuid)  {
> > > -	static int id = 1;
> > 
> > Making id public looks unnecessary to me since after the
> > registration you've got the path which you can pass to the
> > unregistration procedure.
> 
> The id was made public, because service path was not public. We need
> to make either id or service path as public to unregister interface
> path.

Can't you just pass it as user_data to unregister_external_service_reply?

> > >  static gboolean signal_handler(GIOChannel *channel, GIOCondition cond,
> > >  							gpointer user_data)
> > >  {
> > > @@ -524,6 +596,7 @@ int main(int argc, char *argv[])
> > >  	client = g_dbus_client_new(connection, "org.bluez", "/org/bluez");
> > >
> > >  	g_dbus_client_set_connect_watch(client, connect_handler, NULL);
> > > +	g_dbus_client_set_disconnect_watch(client, disconnect_handler,
> > > +NULL);
> > 
> > When exactly would disconnect_handler be called in practice? At
> > least one case seems to be if bluetoothd exits in which case it
> > seems quite wasteful to try to make any method calls to a
> > non-existing service. What other scenarios would disconnect_handler
> > be called in?
> 
> On running the gatt-service, it registers the service and updates gatt db
> with the service path.
> On exiting the gatt-service, it should call "UnregisterService" and clear
> the gatt service db. 

How exactly does gatt-service exit? If it stops iterating the main loop
your D-Bus reply callback would never get called and most of the new
code you're adding would never get run.

> Otherwise, on next run of gatt-service, when it registers the same service
> path, it gets an error, service already exists. 

bluetoothd should monitor all of its clients and clean up after them if
they exit without unregistering. If that's not happening then it's a bug
that's much more important to fix than what you're trying to do here. A
quick look at src/gatt-dbus.c shows that it's at least trying to clean
up, but maybe there's a bug somewhere there.

Johan