Eh, my rule of thumb is that if I can get it done in less than 48 hours, it's not worth pulling in a 3rd party library. Which does error handling different, might have to be hacked around in different ways, and generally just feels ugly.
If Linked-in doc page ( http://developer.linkedin.com/docs/DOC-1008 ) didn't leave out critical pieces of information like (1) The sample consumer_secret that was used (2) The format of the consumer_secret which was used to begin with then I would have had this done a few hours ago I'd bet. Whoever is supposed to manage that doc page at Linked-In is a total slacker. People below in the comments are begging for the above points (1) and (2) to be answered, but nobody has responded in weeks. I'll take a look at that project for some sample code though, thanks :-) On Mon, May 10, 2010 at 5:19 PM, Sixten Otto <hims...@sfko.com> wrote: > On Mon, May 10, 2010 at 12:28 PM, Patrick M. Rutkowski > <rutsk...@gmail.com> wrote: >> I'm really not getting what the "key" argument to CCHmacInit() is >> supposed to be. I'm trying to implement oauth linked-in integration, > > Not really an answer to your question, but are you trying to implement > OAuth from scratch? Is there a reason why you'd choose to do that over > known-working code like http://code.google.com/p/oauth/ ? > > For that matter, if it's LinkedIn you're after, might I humbly suggest > http://github.com/ResultsDirect/LinkedIn-iPhone ? (It's not a whole > solution yet, but should save you some time getting started. And the > engine part shouldn't be iPhone-dependent.) > > Sixten > _______________________________________________ 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 arch...@mail-archive.com
