http://bugzilla.moblin.org/show_bug.cgi?id=5188





--- Comment #22 from pohly <[email protected]>  2009-11-16 14:06:15 PST ---
(In reply to comment #21)
> (In reply to comment #20)
> Yes, that's a problem. I have just tested this and updated the documentation
> accordingly.
> > (In reply to comment #19) 
> > It would be nice for testing, that's all. Is the
> > http://syncevolution.org/documentation/sync-opensync-bluetooth article
> > still-up-to-date?

I moved the documentation page under "Development" because right now, this is
not meant to be used by end users.

> > (In reply to comment #14)
> > > I just pushed the updated code to obex branch.
> > > Patrick, could you give a review?
> > 
> I have updated accordingly, please have a look.

Merged including all "Server Alerted Sync: SAN Parsing" commits. I have not
merged the last two commits:

   CheckDevice: remote device id is allowed to change

In which situation is the remote device ID allowed to change? I can imagine
that there are such situations (SyncEvolution reinstalled from scratch, for
example) which lead to this when matching against the Bluetooth MAC address,
but this should be spelled out in the commit message.

   Obex Client Transport: in-process obex client (binding over bluetooth

Mind the spelling in user-visible text like the SyncURL. I think it is
typically OBEX (all capitals) and Bluetooth. Please check. With that change and
some tweaking of the language + example list the description of syncURL
becomes:

 static ConfigProperty syncPropSyncURL("syncURL",
                                       "Identifies how to contact the peer,\n"
                                       "best explained with some examples.\n"
                                       "HTTP(S) SyncML servers:\n"            
                                       "- http://my.funambol.com/sync\n";
                                       "-
http://sync.scheduleworld.com/funambol/ds\n";
                                       "- https://m.google.com/syncml\n";
                                       "OBEX over Bluetooth:\n"
                                       "- obex-bt://00:0A:94:03:F3:7E\n");

-- 
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to