Hi Wai,

Hmm.. we only made a few changes in the "official" patch:
1) The format string you mentioned
2) The ASCII encoding instead of Unicode encoding that you mentioned
3) Fixed the date timestamp used in the data portion of the
Authorization header

We did not change the factory.MethodOverride=true line as the effect of
this should be eliminated before the variable is used again, if you're
using code such as the following:
---------
GAuthSubRequestFactory authFactory = new
GAuthSubRequestFactory("cl","SampleApp");
authFactory.Token = authSubSessToken;
CalendarService service = new
CalendarService(authFactory.ApplicationName);
service.RequestFactory = authFactory;
--------

I did successfully do queries, inserts and deletes with the 1.0.9 code,
but all my tests were using the actual HTTP method, not the method
override header.  I will have to try testing with the method override
header soon.

Please let me know if the 1.09 code works well for your purposes.

Thanks Wai!

-Ryan




On Jan 15, 6:35 am, "Wai" <[EMAIL PROTECTED]> wrote:
Hi Ryan

Apologizes for not replying sooner as I've just got back from vacation.

I've worked around the problem by commenting out
factory.MethodOverride = true; in the CalendarService constructor
and now secure tokens works under c#! It's really neat!

Yep - had to tweak the library a bit to pass the token. Amongst the
main changes that I can remember making
was correcting the Authorization header format as well as the changing
the signing of data to use ASCII encoding.

Going to get the latest 1.0.9 code now to use the "official" changes.

Thanks for getting back!
Wai


--~--~---------~--~----~------------~-------~--~----~
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://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to