Hi Nami, On Tue, Jun 21, 2011 at 10:14 AM, Li, Nami <nami@xxxxxxxxxxxxxxxx> wrote: > Hi, Luiz >>IMO It should have been named transport instead of protocol, but I don't think it should be exposed in the service driver, actually the transport driver should be the one responsible for authorization. > Well, I think it named transport instead of protocol is really more suitable. Have you reviewed my patch 07/14? Cause I need to know transport type (RFCOMM or L2CAP) when set fd obex transport format (STREAM or SEQPACKET), so I add the member in service drive. First lets get the OpenOBEX patches in so we have an idea how the API will look like, then you can resend the patches so we can review and figure out what is the best way to treat transport types. -- Luiz Augusto von Dentz -- 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
