Bo,

Thank you. That fixed the syncing.

Only one syncml problem remains, duplicate entries are being generated on 'updated' entries. As an example I added a home phone number to an entry. The result were duplicate entries in both the client and server side. The result was the same in both directions, i.e. client to server and server to client.

Regards,
Dan

Bo Lincoln wrote:
The SyncML plugin can, so far, only sync over the internet. This means
that all fields are related to normal internet addresses, URL's etc.

  
 What goes in the server name field? an ip address? which one?, 'local' 
 or 'remote'? Can it be a host name? If so can it be an alias? 
    

If you are configuring a client, this is the address of the server. It
can be a host name, IP address, or alias. Just like a normal URL.

  
 What goes in the path section? The remote path? If so to what?? (Path as 
 a model does not make sense to me here.) 
    

Again, if you're the client, this is the path of your syncml server.
Many SyncML servers are servlets in a normal web server, so you have to
be able to give a full URL. If you are a server, you can ignore this
field.

  
 How is Authentication filled out? is it user id and password?  Or is a 
 unique pair chosen for Multisync? Cat is be a variable unrelated to the user??)
    

The auth user id and password can be anything you want. Note that the
password will be stored on disk in clear text, so don't choose your most
secret password. (As long as you use https:// connection it will never
be sent over the net in clear text, though.)

/Bo

  

Reply via email to