Author: fmantek
Date: Tue Aug 28 23:13:20 2007
New Revision: 223

Modified:
   trunk/clients/cs/RELEASE_NOTES.txt
   trunk/clients/cs/src/core/gauthrequest.cs

Log:
made GAuthToken public

Modified: trunk/clients/cs/RELEASE_NOTES.txt
==============================================================================
--- trunk/clients/cs/RELEASE_NOTES.txt  (original)
+++ trunk/clients/cs/RELEASE_NOTES.txt  Tue Aug 28 23:13:20 2007
@@ -7,6 +7,8 @@
 - fixed typo in the blogger sample (www..blogger), which made the sample hard 
to use
 - added the ability to use authsubtokens to the ExecRequest utility (including 
exchange of a onetime
   token to a session token). Just run ExecRequest for the command line 
parameters
+- make the GAuthToken property of the GAuthRequestFactory public. It was 
mistakenly marked internal, so that
+  the token could not be retrieved by a client application for caching.  
 
 == 1.0.9.9 ==
 - added GBase support for m:adjusted_name and gm:adjusted_value inside 
attributes

Modified: trunk/clients/cs/src/core/gauthrequest.cs
==============================================================================
--- trunk/clients/cs/src/core/gauthrequest.cs   (original)
+++ trunk/clients/cs/src/core/gauthrequest.cs   Tue Aug 28 23:13:20 2007
@@ -144,7 +144,7 @@
         //////////////////////////////////////////////////////////////////////
         /// <summary>Get/Set accessor for gAuthToken</summary> 
         //////////////////////////////////////////////////////////////////////
-        internal string GAuthToken
+        public string GAuthToken
         {
             get {return this.gAuthToken;}
             set {

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google 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-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to