Hi Waldemar, * Waldemar.Rymarkiewicz@xxxxxxxxx <Waldemar.Rymarkiewicz@xxxxxxxxx> [2010-11-10 13:12:53 +0200]: > Hi Marcel, > > >> + void Disable() > >> + > >> + Shudown SAP server and remove the SDP record. > >> + > >> + Possible errors: org.bluez.Error.Failed > > > >I don't like this. If you have properties then just changing > >the property should be enough. So a SetProperty is more appropriate. > > I see another option to get rid of 'Enabled' property and leave the methods. What would you say on that? It's not a good a idea. We have been moving everything we can to a set property operation instead of a method call. Do that as method is add unnecessary code to BlueZ once we already have set property there. > > >> + > >> + void Disconnect(boolean type) > >> + > >> + Disconnect SAP client from the server. > >The 'type' > >> + parameter indicates disconnection type. > >> + > >> + True - gracefull disconnection > >> + False - immediate disconnection > >> + > >> + Possible errors: org.bluez.Error.Failed > > > >I don't like this style of method names at all. Using method > >names like GracefulDisconnect and ImmediateDisconnect would be better. > > That's fine. > > >However I am not sure we should differentiate here at all. We > >should always to the graceful disconnect. What will the > >immediate disconnect bring us? > > That's actually intended for testing only. One of PTS test cases expects the tester to trigger immediate disconnect. > In practce, it is only used when connection to sim card is lost, but this is obviously done internally. So this shouldn't be in the API, no one is going to use it. You can create something internally for the immediate disconnection that you go and set manually inside the code. Make sure to comment in the code why you are adding this there. That can also be a option in some of the bluetooth config files. Let's see what others think here. -- Gustavo F. Padovan http://profusion.mobi -- 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
