RE: [PATCH obexd 06/14] Add protocol member to distinguish OBEX Protocol.
From: Li, Nami <hidden>
Date: 2011-06-21 07:14:50
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. Thanks. Nami