[Thread Prev][Thread Next][Thread Index]
One db, multiple conduits?
- To: pilotmgr@xxxxxxxxxxxxxxxxxxxx
- Subject: One db, multiple conduits?
- From: Martin von Weissenberg <Martin.von.Weissenberg@xxxxxxxxxxxxxxx>
- Date: Tue, 17 Feb 1998 10:02:14 +0200
- Sender: owner-pilotmgr
Hello all!
I've been playing with the idea of writing an address book conduit that
would sync with several databases. For example, I want to transparently
sync a certain category, let's say "Friends and family" with the
corresponding category in my girlfriend's Pilot, and another category
"Orchestra members" with some Pilot owners in my orchestra (this
involves shipping the database back and forth over the Internet).
Actually, the conduit need not be limited to address books, but could
handle To Do databases, HMaki high score tables or whatever. I have the
procedures clearly thought out and can supply more gory details and
information sources if someone is interested.
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
Martin von Weissenberg <http://www.hut.fi/~mweissen>
"You know, of course, that the Tasmanians, who never committed adultery,
are now extinct." (M. Somerset Maugham)
------------------------------------------------------------------------
***********************************************************
* This is a public mailing list! *
* Please do not publish Sun proprietary information here! *
* - - - - - - - - - - - - - - *
* http://www.moshpit.org/pilotmgr *
***********************************************************
|
|