On Tue, 2004-12-14 at 15:36 +0800, Gideon N. Guillen wrote:

Hi and thanks for all your answers.

> On Mon, 13 Dec 2004 20:10:35 +0200, Mika Raento
> <[EMAIL PROTECTED]> wrote:
> > 1. Multisync doesn't store a copy of the devinf from the device nor
> > request it. If the device doesn't send it (like a 7650 never does after
> > the initial connection), then MS doesn't know e.g. what version of iCal
> > it should send. A 7650 can only handle 1.0.  The handling of devinf
> > should probably be done by somebody more familiar with the codebase.
> 
> Not really a problem. The SyncML spec did not mention anything like
> this. I guess, what we can do on the side of MultiSync is to send a
> "Get" command to request the device profile everytime you sync.

This is the only one I disagree with. The device explicitly sends a
'Put' with its devinf, which in my understanding _is_ a request for the
server to keep a copy of it around for future reference.

So we should probably keep all the devinf's we receive somwhere in
the .multisync/<pair>/ directory, and retrieve from there when we get a
connection.

> The client is supposed to send an error if the server sends a
> Target/LocURI that does not exist on the client side. I think the best
> thing to do if we encounter something like this is to do a Slow Sync
> on the next sync session (client sends all data, then server send data
> not yet on client).

This sounds better, right.

        Mika

-- 
Mika Raento           mailto:[EMAIL PROTECTED]       http://www.iki.fi/mikie/
"You can't *ADD* things and come out with *LESS* than you started with!"
"I  can  do  that!  It's  a  free  country!  I've  got  my  rights!"
                                      -from Calvin & Hobbes by Watterson




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Multisync-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-devel

Reply via email to