Date: Sat, 12 Apr 2008 19:26:12 +0100 (BST) From: Iain Hibbert <plunky@rya-online.net> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth application Message-ID: <1208024773.051889.1001.nullmailer@galant.ukfsn.org> In-Reply-To: <bb4a86c70804121003i2266364en33b9d6f3056daffa@mail.gmail.com> References: <20080410230521.027b3b78.saamii@gmail.com> <bb4a86c70804101558x19bdbdasf1d8be910651df74@mail.gmail.com> <20080412022834.4b36e8c0.saamii@gmail.com> <bb4a86c70804121003i2266364en33b9d6f3056daffa@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 12 Apr 2008, Maksim Yevmenkin wrote: > what is not "easy" about obexapp? are there any particular features > that you are missing? One thing that I have been meaning to add but haven't found the time, is that when obexapp runs in server mode, it would be good to run different services (OPUSH/FTRN) on different channels as currently they run on the same channel. The reason I want this is so I can require authorisation for FTRN but allow OPUSH to anybody. The context methodology that obexapp uses should be fairly easily extendable for this, though I found the openobex API to be complex and it might be simpler to make each service run as a separate instance. If you are planning to work on bluetooth infrastructure (what, child grown up already!? :) then even though I don't use FreeBSD, I suggest: + "Link Mode" enable AUTH and ENCRYPT flags for individual L2CAP or RFCOMM channels (eg for above). I also did SECURE (ENCRYPT plus refresh link key) and worked on MASTER but had limited success so thats on hold for now. + removal of ng_ and NG_ prefixes from public API (HCI and L2CAP IIRC) will make porting programs much easier.. I would recommend that you can take the hci.h and l2cap.h defs from NetBSD files so that the spelling is constant throughout the BSD family at least. (also, I added HCI 2.1 already) + commit the SCO code you mentioned the other day you said you didn't know how it could be used, but until it is public then of course nobody else can work on that :) regards, iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1208024773.051889.1001.nullmailer>