Re: [Bluez-devel] Announce : BlueZ-based implemantation of JSR82

Marcel Holtmann
2004-05-25T15:07:40Z

Hi Julien,

> There are main reason why I rewrote some BlueZ functions is that:
> - Functions like "sdp_service_search_attr_req" return a list of
> sdp_record_t. If I had to parse these sdp_record_t in order to
> construct the requested Java Objects, this would have been an amazing
> amount of switch or if statement. The best solution was therefore to
> directly send the bytes to the java implementation.

put this problem up in a seperate thread on the mailing list and tell
how the Java Objects have to look like. We should find a better solution
for that.

> > What I also don't wanna use is somekind of "de.avetana.bluetooth" vendor
> > extensions. If something is not possible in pure Java JSR-82, sorry not
> > my bad ;)
>
> JSR-82 provides just the minimal amount of classes. It lets the
> programmer use "background classes" but this is transparent for the
> end-user (I will give some example of this transparency in the future
> how-to). These de.avetana.bluetooth.* classes are really needed to fully
> implement all javax.bluetooth.* classes.

You must explain this to me in detail, because I don't understand why.
Actually I think we should avoid this.

> > The native interface should only be a wrapper. Let's talk about the
> > stuff and put some of it back to the Bluetooth library where it should
> > belong.
>
> I would say that 90% of the native interface is today a wrapper. Only
> the service search uses home-made-functions derived from the BlueZ code.

As said already, lets fix this in the Bluetooth library itself. I know
that SDP itself is a horrible mess of object oriented stuff, but I think
we will find a solution for it.