On Fri, 6 Aug 2010, Scott Haneda wrote:

>> 1. There is _no_ native oauth support in curl/libcurl right now.
>
> I was surprised by the post; excited if it were true, but wondering where
> curl draws the line in what it supports.

There is no distinct line. curl, and libcurl, is about doing file or data
transfers with application layer protocols and offering enough features to do
the job really well. What line is that?

I also want the line to be drawn by us, the people in the curl and libcurl
users and hackers community - and not by any specific individual. What should
curl do? What should it not do? Nothing is exactly black or white!

> Aren't there plenty of oauth libraries out there already?

There are. Possibly one of them could be used to make curl support it.

>> 2. There is _no_ ongoing work on implementing oauth other than what has been
>> mentioned on the libcurl mailing list a few months ago and since nothing
>> has been heard about it since I suspect there hasn't been a lot of
>> progress.
>
> Do you have a link to that discussions archive?

http://curl.haxx.se/mail/lib-2010-05/index.html#73 and
http://comments.gmane.org/gmane.comp.web.curl.library/27901

(The same thread, stored at two different places.)

> Or is oauth the modern day http auth and something that indeed should be
> part of any any tool that pushes and pulls resources.

I would say that IETF documented protocols at least reach above a lowest
acceptable level, but there's no clear rule.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html