David A. Desrosiers wrote:

 >> Except for ColdSync not sending the updated creation date to the
 >> Palm (requiring me to delete the metadata file by hand with
 >> Z'Catalog),
 >
 > Why not just use whatever facility is in Coldsync that implements the
 > dlp_DeleteDB function, and delete the metadata db before you sync a
 > new copy to your Palm? ..or use pilot-link, which can do this without
 > effort.

Ah, excellent question. I have access to the DLP functions only in a 
"sync" conduit (even though the "fetch" part occurs while we are 
connected with the Palm, and could theoretically use the DLP functions). 
If I make my conduit a "sync" conduit, I forfeit the generic backup sync 
conduit (I'd have to do the same work as the sync conduit myself).

There are a few things that could be done in ColdSync to improve this. 
"fetch" conduits could have access to the DLP functions. There could be 
a way for a "sync" conduit to "decline", like Apache's handlers (so you 
do a bit of work, like delete the metadata PDB on the Palm, then let the 
generic conduit do its usual work). Or even, it could just update the 
creation/modification dates! :-)

Why not use pilot-link? Both me and my girlfriend use Palms using the 
same computer. We both want "drop the Palm in the cradle, push the sync 
button and take it back" capability, without any interaction with the 
computer (its my "server" box, the monitor is often turned off, nobody 
is logged it, sometimes there's no monitor at all).

ColdSync's daemon mode is exactly what I want, while it doesn't seem 
like pilot-link can do what I want, at least not out of the box (I have 
just added a "coldsync -md" line in my /etc/inittab, with the 
appropriate "palms" lines).

-- 
Pierre Phaneuf
http://advogato.org/person/pphaneuf/

_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev

Reply via email to