Hi Slawek, On Mon, Dec 13, 2010, Slawomir Bochenski wrote: > In order to fully implement Message Access Profile, support for more > than one so-called instance is needed (MAP specification, chapter > 3.1.8). According to specs, separate e-mail accounts on MSE should be > represented by separate MAS instances. This requires one SDP record > per instance and those differ by MASInstanceID and ServiceName. > > As I understand this also implies that each and every instance needs > its own separate RFCOMM channel? Yep, I think that's implied, since othewise we can't detect which MAS instance the client is trying to connect to (if I read the spec correctly). > What would be the preffered way to deal with this ugliness in obexd > code? Since we're primarly conserned with supporting only SMS for now, I think it's too early to start adding complexity to the code due to this feature. I.e. let's get working MAP with SMS support integrated upstream and only after that start looking into these more advanced features. > If separate channels are needed how to keep this in compliance > with bluez doc/assigned-numbers.txt? We'll need to reserve some channels for additional MAS instances. > And what about assigned bitmask values for services in src/obex.h? Do we need to change something there? 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
