Thanks for the info. Alex. Right, the code in question uses the
Address Book framework, and all the sync logic was worked out and has
been performing well. Since this work was originally done for 10.2,
Sync Services wasn't around yet. Ideally, all of the AddressBook
framework calls would go away and we would use Sync Services instead.
So, do you make SOAP calls outside of the Sync framework to move data
to/from the server, or is there a way to set up a Sync Services client
that talks to the server directly? It's not clear to me if Sync
Services can handle the communication, if it gives you hooks to
perform that communication, or if it just works off of data that I
need to get to the local machine. Also, what is the data that you
store on the server? Is it the truth database, Address Book data or
something else... Or, do you not have to put the data on the server
because the web database is specified in the schema or something like
that, and Sync Services handles the data transfer for you?
I'm trying to understand the how the client/server communication
works. I couldn't find a good explanation of this in the docs.
Thanks,
- d
On Mar 21, 2008, at 2:13 PM, Alexander F. Hartner wrote:
Hi Dave,
I have also been working on something quite similar to this for some
time now, however I have been using Sync Services. Take a look at
http://www.addressbookserver.com which uses WebServices (SOAP) to
transfer Address Book content to a central server, which is also
platform independent. The server can be configured to use most modern
relational database and could potentially be used for all sorts of
integration with other applications / purposes.
What framework are you currently using to access the Address Book
content. Sync Services present quite a different interface, compared
to
the older Address Book API. Sync Services is quite useful as it
figures
out the differences between the server and each client for you,
however
it seem that you already bridged this hurdle.
The SyncServices framework basically handles 2 types of events, a push
(writing to the truth db) and a pull (when you read from the truth
db).
During each interaction the you would first perform a push, then the
sync engine will figure out the difference and provide you the changed
during the subsequent pull. The type of objects uses a nested
directories, which are not directly modeled on the underlying data,
but
rather able to pass the data in a generic way. So you don't get the
same
object model used by the Address Book API.
Have fun
Alex
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
