Hi,
today I played with various schemes for consistent obex URIs. This has
been a To Do for some time now.
I tried mixing the transport with protocol+service. (Maybe this is wrong
altogether and we need to wrap the protocol+service with the transport
-- or the other way around. I couldn't figure out a nice scheme for that
though.)
We have these
protocol := obex
service := push, ftp, sync (and others like bpp, bip, ...)
transport := ir(irda), bt(bluetooth), usb, net, cable
transport specific authorities (aka target address)
ir: ?
bt: 00-11-22-33-44-55:6 | nickname:6
usb: :1 (host is implied)
net: server:651 | 1.2.3.4:5
cable: /dev/tty0 (but slashes wont work...)
Reading the URI RFCs (rfc3986) it leaves us to choose from (and maybe
others?)
obex:ftp:bt:00-11-22-33-44-55:6/some/file
obex:sync:net:my.server.tld:651/telecom/cal.vcs
- vs -
btobexftp://00-11-22-33-44-55:6/some/file
netobexsync://my.server.tld:651/telecom/cal.vcs
- vs -
obexftp+bt://00-11-22-33-44-55:6/some/file
obexsync+net://my.server.tld:651/telecom/cal.vcs
I could parse and use all of them. The question is which scheme to
suggest to users?
I'd prefer the last one. The first one I think is recommended by the URI
RFC but looks strange (because there is no "://" part). Also it implies
a hierarchy and the transport is not related to the service.
The second one is just clumsy and difficult to read or spell.
Any comments are much welcome.
cu,
Christian
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Openobex-users mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/openobex-users
