From: Christian W. Z. <Christian@Zuckschwerdt.org> - 2006-05-29 17:02:28
|
Hi, Marcel Holtmann wrote: >I tried to come up with some general Bluetooth URIs and failed so far, >but you might wanna have a look at the JSR-82 specification: > > The protocol is fixed to "btspp". It's short and meaningful but very specific. I'm still not convinced that mixing the service and transport part is a good idea. Just think about tunnels or converters. One interesting point in JSR-82 is the fact they use a UUID as pseudo port number. (e.g. btspp://localhost:F9EC7BC4953C11D2984E525400DC9E09/). Placing the service that way is a nice approach. On the other hand it would seriously cripple the possiblilities. There is no way to discover the port number when accessing an obex server over the net. And perhaps one would like to use a some service on a given bt channel. >I personally like to see a more general approach instead of an OBEX only >one. Application like Gnome-VFS etc. would also profit from a general >scheme. > > I second that. If something like an URI scheme is going to appear in ObexFTP it should be as general as possible and agreed upon by all interested parties. Perhaps everyone interested could spell out their requirements. cu, Christian |