http://bugzilla.moblin.org/show_bug.cgi?id=9446
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2010-02-04 00:29:24 PST ---
I updated the syncURL help text:
$ src/syncevolution --sync-property syncURL=?
'--sync-property syncURL=?'
Identifies how to contact the peer,
best explained with some examples:
HTTP(S) SyncML servers:
http://my.funambol.com/sync
http://sync.scheduleworld.com/funambol/ds
https://m.google.com/syncml
OBEX over Bluetooth uses the MAC address, with
the channel chosen automatically:
obex-bt://00:0A:94:03:F3:7E
If the automatism fails, the channel can also be specified:
obex-bt://00:0A:94:03:F3:7E+16
For peers contacting us via Bluetooth, the MAC address is
used to identify it before the sync starts. Multiple
urls can be specified in one syncURL property:
obex-bt://00:0A:94:03:F3:7E obex-bt://00:01:02:03:04:05
In the future this might be used to contact the peer
via one of several transports; right now, only the first
one is tried.
Congwu, is this okay? In "pohly" branch.
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.