Why have you chosen a architecture that requires our data to be on handled by an intermediary server? What are the advantages, and what are the challenges in providing the service with this architecture. ?
Who hosts the spanning sync service? Where is the spanning sync sever box located? You state in the FAQ that it is more secure architecture. Please can you elaborate? I'm coming from the position that from a security aspect involving a third party in security terms is always inherently less secure. It's weighting of flexibility over security. What processes to you have in place to mitigate that? How often do Google change there Calendar API? Sorry for these direct questions, but i had no idea my data was being handled elsewhere. Thanks Bill 2009/3/1 cwood <[email protected]> > > That's right. Your calendar and/or contact data is processed on our > servers, which act as an intermediary between Google and the client > running on your Mac. The communication between the Spanning Sync > client and our servers is all SSL-encrypted. Your password though goes > directly from your Mac to Google, also over an SSL-encrypted > connection. > > Regards, > Charlie > > > On Mar 1, 6:54 am, Bones <[email protected]> wrote: > > Interesting. > > > > So, during a sync, my data is passed through your servers before being > > forwarded to Google? > > > > Just trying to understand the architecture ... > > > > Bones > > > > On Mar 1, 12:47 am, cwood <[email protected]> wrote: > > > > > the actual sync, much of which > > > takes place on our servers, which in turn talk to Google. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Spanning Sync" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/spanningsync?hl=en -~----------~----~----~----~------~----~------~--~---
