Geek Answers Handbook

OAuth vs. Portable Contacts to import contacts

We are currently using an outdated screen scraper to import contacts from gmail / yahoo / etc. I want to update this to use the new OAuth-based APIs so that users cannot enter their credentials on our site. I'm really intrigued by the work that Plaxo does with Portable Contacts , which Google also supports. This seems like a good direction for read-only access, and it is still supported by OAuth.

Are there any good reasons to just go with the standard OAuth API for these providers instead of taking the Portable Contacts route? I would like to know if there are good reasons to avoid this. I will continue to use direct OAuth for those who do not support PCs, so this is not a matter of development time, but rather support and confidence in the new approach.

+5
source share
2 answers

The idea is that each OAuth implementation will be slightly different, since each portable contact implementation will be the same. This is similar to the REST API (OAuth) compared to the SOAP API (Portable Contacts - but with the same overhead as OAuth).

, - , , .

, , , OAuth- . ( OAuth - , , , ).

+1

OAuth Core ( URL- OAuth, ), ( , ). , , ad-hoc ( , , URL-). Portable Contacts , . , , , OAuth Core .

OAuth Discovery, , , , .

0
source

More articles:


All Articles