Alright, thanks. Yes it is large which is why I was asking, and I didn't
know about the freeze.
> In the mean time, you can work on adding a bunch of tests for this
functionality and some docs on how to use it with libcurl.
I'll look at the test infrastructure. RE; docs on how to use it with
libcurl, where would that go? I've made it so that curl --libcurl will
produce decent examples, e.g.:
struct curl_oauth2_token token;
token.token_type = CURL_OAUTH2_TOKEN_TYPE_MAC;
token.access_token = "26267";
token.mac_token.mac_key =
"239c1faa2d85bf762bd5a93c2467957ec7be9fc67d18c76d";
token.mac_token.mac_algo= CURL_OAUTH2_MAC_ALGO_HMAC_SHA256;
/* Š */
curl_easy_setopt(hnd, CURLOPT_HTTPAUTH, (long)CURLAUTH_OAUTH2);
curl_easy_setopt(hnd, CURLOPT_OAUTH2_TOKEN, &token);
Are you talking about other examples in the docs/examples directory or
pure documentation, and where?
YA
Learn about GPT services and architectures on Confluence.
<http://confluence/display/GPT/GPT+Architecture>
On 2/1/13 2:44 AM, "Daniel Stenberg" <[email protected]> wrote:
>On Thu, 31 Jan 2013, Yves Arrouye wrote:
>
>> Is there no interest in this? If so, is it because of the domain (OAuth
>>2.0
>> tokens) or the structure of the patch, or its size, orŠ? I'm curious.
>>We'd
>> love to be contribute this back to the community.
>
>I am interested. But you happened to post this patch during a feature
>freeze
>period when I'm already struggling hard to get bug fixes in and another
>release out next week. Until then I simply cannot review such a large
>patch.
>
>In the mean time, you can work on adding a bunch of tests for this
>functionality and some docs on how to use it with libcurl.
>
>Unfortunately we're not that many developers here and we're all mostly
>doing
>this on our spare time. Some things just take time.
>
>--
>
> / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
