Hi Hendrik, On Wed, Sep 15, 2010, Hendrik Sattler wrote: > > Do we really need BT interface discovery/search API in openobex? I > > think Bluez covers that pretty well, no? > > Even Linux(Bluez) and *BSD have a complete different code how to do > this just for bluetooth device enumeration. Windows is also totally > different. The patch[0] is _only_ for HCI enumeration! > SDP is a different beast (again, each a differnt implementation).
Well, you're doing a fully fledged inquiry and on top of that name resolving for each discovered device (which involves a baseband page operation). Both of these operations are very time consuming (inquiry typically around 10 seconds and each name query can be up to 5-20 seconds depending one which devices are still within range and what the configured page timeout of the local bluetooth adapter is). BlueZ already stores information about previously discovered devices (including paired ones) so you're potentially doing quite time consuming actions here for something that might not be necessary at all. Another problem I see is that this is a blocking API without any non-blocking alternative while most other things in openobex can be done fully asynchronously in a single thread. Thirdly, you're accessing the raw HCI layer here and it's likely that in the future it'll require special privileges from the process (it does that already now for certain HCI commands), in which case this isn't suitable for a user application. Johan ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
