Hi Tom, On Mon, Jun 14, 2010, Counihan, Tom wrote: > Please find below proposed Bluetooth MAP API, based upon Message > Access Profile, ver 10r00. It'd have been good to clearly state that you're only talking about the client side of MAP (it became clear to me only after noticing that you've got org.openobex.client in the D-Bus API). The server side would e.g. be implemented through an obexd plugin. > Comments most welcome. > Of note below is missing the PushMessage function - Section 5.8 of > mentioned spec. > Reason being, I'm trying to get my head around what should be returned > from a GetMessage call below, and conversely what should be passed to > a potential PushMessage - bMessage can take on a number of different > guises. > Any guidance/opinion would be greatly appreciated in this area, or any > other suggested improvements. Are you sure you want to use D-Bus for this? I suspect the required bandwidth will be too high to be efficiently handled using D-Bus. Wouldn't a MAP specific library on top of OpenOBEX make more sense? 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
