>>>>> "RW" == Ronan Waide <[EMAIL PROTECTED]> writes:
RW> Just to poke my oar in here; There should, in CVS, be a big chunk of
RW> code for merging/syncing any old bbdb into your regular bbdb.
I'd like to start some sort of architectural discussion on this
topic. Over the long US holiday I finally got together a web page
for my Palm<->BBDB conduit:
http://home.rochester.rr.com/tsdeweese/SyncBBDB.html
My conduit is based on Perl, not because I think Perl is a great
language, but because I felt it was important for conduits to plug
into a Synchronization Manager (my reasons are given on the web page),
(the most flexible, only?, manager at the time was PilotManager, which
used Perl).
While I suppose it's possible for emacs to be that Synchronization
Manager I don't think it's the most appropriate host (perhaps others
disagree?). On the flip side many of the more complex synchronization
customizations (like record filtering, complex field mappings) would
be much easier to accomplish in e-lisp (mostly because you can expect
users to write bits of code for you that you simply call) than in
Perl.
Do people have opinions on what they think the 'ideal' system
would be? For what it's worth, I'm not overly attached to my conduit
but as with most things people write (mostly) for themselves it does
what I need it to, which currently puts it ahead of the alternatives:)
I really wanted to get it out there so people could take a look at
it comment and try to make decisions about where the BBDB community
would like it's Palm synchronization direction to be (for those that
care of course).
RW> There should also be a large part of the code necessary to get the
RW> pilot database into the bbdb, [...]. The solution I was working
RW> towards was that Dinesh's code or my code or any other code
RW> (e.g. LDAP merge, WINCE merge, etc.) could feed into the generic
RW> merge code and allow people to build conduits for whatever they
RW> like, safe in the knowledge that there's a generic backend to do
RW> the merge/sync operation.
This an attractive idea, thoughts on how to avoid having to do a
full sync (transfer the whole address book from the palm) every time
to perform the merge? How is record matching being accomplished
(given that names/email addresses are no longer unique :).
--
Thomas DeWeese
[EMAIL PROTECTED]
"The only difference between theory and practice is
that in theory there isn't any." -- unknown
_______________________________________________
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/bbdb-info
