Thoughts on libsoylent re: Conduit

["John Stowers" <john stowers gmail com>]

Hi Guys,

I finally found the time to look over the luibsoylent 2.0 API, specifically evaluating it WRT synchronization, and how compatible it is with Conduits way of thinking. I was wondering if you could clarify a few points

* Conduit requires some fixed UUID type representation for an addressbook (that you wish to sync). I noticed that you can get the underlying EBook using the 'ebook' property of SLBook. It would be convenient to also have a sl_book_get_uri() which returns the underlying EBook uri. It would then make sense to add a sl_book_open_from_uri() calls. The necessity of these both depend on how frequently one might use solylent with multiple addressbooks
* It would also be good to have the ability to get similar information for the SLPerson. This would likely be sl_person_get_uid() and return the underlying EContact E_CONTACT_UID field.
* Is it possible to delete a SLPerson from a book when unable to get construct that persone. Something like sl_book_remove_person_by_uid().

The point of all of this is to have some invariant way of representing Contacts and Addressbooks. It should be noted that these function may just be duplicates of information already available in lower layers, but it makes binding the library from python a lot easier.

Thanks,

John