Yes. I noticed the example at
http://code.google.com/apis/accounts/docs/OAuth.html#GoogleAppsOAuth
and another at
http://code.google.com/apis/accounts/docs/OAuth_ref.html#SigningOAuth
less than an hour after my last post to this thread. Now, I just need to
figure out how to send it.
The service in question, at least for my proof-of-concept, is still the
calendar retrieval service, a "GET" service. Do all these parameters just
get inserted into the URL? If so, then how are they punctuated?
The parameters for the "http_url_get" call in the aforementioned "HTTPAPI"
are:
> peURL
> peFilename
> peTimeout
> peUserAgent
> peModTime
> peContentType
> peSOAPAction
>
with peURL being the URL being requested, much the same as if I were
issuing the request from a browser (and indeed, for my "magic cookie" test,
I did it in a browser first, then once I had it returning a JSON data
stream, I just cut and pasted it into my test program), peFilename being
the local file into which to pour the response, and the remaining
parameters (all optional) being self-explanatory.
--
You received this message because you are subscribed to the Google
Groups "Google Calendar Data API" 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://code.google.com/apis/calendar/community/forum.html
