* Bo Lincoln schrieb am 10.09.03 um 09:09 Uhr:
> Hello, I'll answer the first and Tom will have to answer the second
> question:
> 
> > 1. Does it support two-way synchronization? By two-way, I mean both side
> > will have a union of the dataset from both side, and conflict will be
> > prompt to user for solution.
> 
> Yes, MultiSync does only two-way sync. As for conflicts, MultiSync
> currently solves them by duplicating both entries so you'll have to
> resolve the conflict either in Evo or in the Zaurus. It does detect if
> the two entries are identical, though.
> 
> /Bo
> 

Hi Bo!

I think it would be great if MultiSync could tell the user about
conflicts in some way... I for example always do a manual sync by
pushing the [Sync] Button. No automatic sync. This is interactive.
And I would love it if multisync would tell me about conflicts in
this case. Maybe this could be dependent on the "Automatic
synchronize" Setting being set to manual...

And I have one question:

I hav one Mobile, a Workstation and a Laptop. I want to keep
Evolution on the Laptop and on the WS keep in sync via my mobile. Is
that problematic? What is the best way to set it up to not confuse
multisync? 

[Workstation Evo] <---> [Mobile] <---> [Laptop Evo]

or is something like that a better solution:

[Workstation SyncML] <---> [Laptop SyncML]
                       +
   [Workstation Evo] <---> [Mobile]


And until now I didn't manage to sync via SyncML.
Maybe I am too stupid for that:

    Syncpair on WS: Evo <--> SyncML Server
Syncpair on Laptop: Evo <--> SyncML Client

User and password set on both sides. Connect seems to work, but no
data is being synced. What has to be done in preparation to make
this work? What about that UTF-8 bug (?) is that responsible?

Serverside debug output:
###############
SyncML:  Get changes, mode 0
SyncML:  Got engine cmd: 6
SyncML:  Action: 1 0 0
SyncML:  SyncML disconnected.
SyncML:  SyncML server: Got error 5.
SyncML:  Client connected from 192.168.1.99.
SyncML:  Using SyncML 1.1
SyncML:  Action: 1 0 0
SyncML:  Using SyncML 1.1
SyncML:  Authorization succeeded.
SyncML:  Last anchors differ (1063185722-(null)), do slow sync.
SyncML:  Found DB pair: addressbook - addressbook
SyncML:  Last anchors differ (1063185722-(null)), do slow sync.
SyncML:  Found DB pair: calendar - calendar
SyncML:  Manufacturer: The MultiSync Project
SyncML:  Device ID: A4600A91DAC4
SyncML:  Device type: workstation
SyncML:  Action: 1 0 0
SyncML:  Received device info.
Entity: line 2286: error: Input is not proper UTF-8, indicate
encoding !
SUMMARY:Zv künd¼RS
                              ^
Entity: line 2286: error: Bytes: 0xBC 0x52 0x53 0x0D
SUMMARY:Zv künd¼RS
                              ^
SyncML:  Action: 0 0 0

###############
Clientside debug output:
###############
Got message 6
SyncML:  Got change notification. Getting changes.
Got message 9
Get changes done.
SyncML:  Got engine cmd: 1
SyncML:  Action: 1 0 0
SyncML:  Looking up 192.168.1.100
SyncML:  Connecting to 192.168.1.100...
SyncML:  Using SyncML 1.1
SyncML:  Action: 1 1 0
SyncML:  Using SyncML 1.1
SyncML:  OK, I'm authenticated.
SyncML:  Manufacturer: The MultiSync Project
SyncML:  Device ID: C4FA434A0C3F
SyncML:  Device type: workstation
SyncML:  Slow sync requested by other side.
SyncML:  Found DB pair: addressbook - addressbook
SyncML:  Slow sync requested by other side.
SyncML:  Found DB pair: calendar - calendar
SyncML:  Action: 1 0 0
SyncML:  Received device info.
SyncML:  Getting changes again.
Got message 9
Get all done.
SyncML:  Got engine cmd: 1
SyncML:  Action: 1 0 0


-Marc
-- 
BUGS My programs  never  have  bugs.  They  just  develop  random
     features.  If you discover such a feature and you want it to
     be removed: please send an email to bug at links2linux.de 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Multisync-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-devel

Reply via email to