Re: One db, multiple conduits?

[mindless (Alan Harder)]

> Now getting down to the real question: can I sync with my address book
> conduit as outlined above *AND* with Alan Harder's upcoming address book
> conduit *WITHOUT* problems like changes not propagating correctly or
> even propagating at all?  Is it even worth contemplating such a conduit
> or should I hack this functionality into Alan's conduit when he's
> finished with it?

Martin,

As you probably know, the pilot maintains a "modified" flag for all pilot
records.  To make synchronizing faster, most conduits use the
getNextModRecord() method to retrieve only changed pilot records and avoid
downloading the whole database.  At the end of the sync the modified bits are
cleared, since all the changes have presumably been copied over to the desktop
side.

So, two conduits using the above model would NOT work together, since the
second one to run would not see any modified records.  However, you can
write a second conduit using the same database as long as you don't clear
these flags.  You described only looking at records in certain categories..
you could load all records in the category you're interested in and compare
them to your own db file to see what's changed.. then it wouldn't matter if
your conduit ran before or after another conduit which clears the modified
flags.

	- Alan
------------------------------------------------------------------------
***********************************************************
*             This is a public mailing list!              *
* Please do not publish Sun proprietary information here! *
*        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
*             http://www.moshpit.org/pilotmgr             *
***********************************************************