Hi Suraj, On Tue, Sep 07, 2010, Suraj Sumangala wrote: > +Methods void RegisterAgent(object agent) > + > + This registers the Sim Access adapter agent. > + This also registers the profile with the service > + Databse and start waiting for an RFCOMM connection > + on the SAP server channel. > + > + The object path defines the path the of the agent. > + > + If an application disconnects from the bus all > + of its registered agents will be removed. > + > + Possible errors: org.bluez.Error.InvalidArguments > + org.bluez.Error.AlreadyExists > + org.bluez.Error.Failed > + > + void UnregisterAgent(object agent) > + > + This unregisters the agent that has been previously > + registered. The object path parameter must match the > + same value that has been used on registration. > + > + Possible errors: org.bluez.Error.DoesNotExist > + org.bluez.Error.InvalidArguments > + org.bluez.Error.Failed So you have these nice agent registration methods, however where's the definition of the agent interface? And if you're going to use an agent for this (which seems like a good idea) the SAP commands should map to D-Bus method calls to the agent and the D-Bus method replies from the agent should map to the SAP replies. I.e. please get rid of the D-Bus signals and methods you currently have for this. Btw, I'm not 100% convinced that this is the most sensible architecture for implementing SAP, but assuming that it is the above comments apply :) Johan -- 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
