Re: Re: prevPageToken problem

I thought I'd through out for comment how I intend to approach the 
prevPageToken issue.

As the user pages through the list of posts, I intend to "remember" the 
nextPageToken from the preceding page.  That becomes the page token for the 
current page (i.e., the currentPageToken.  I then use that along with the 
nextPageToken for the current page to build up a hash.  The "keys" of the 
hash will correspond to values for the currentPageToken while the "values" 
of the hash will correspond to the values of the nextPageToken.  So for any 
given page, I can grab the value of the nextPageToken for that page and use 
it to obtain the currentPageToken from the hash.  Once I have the 
currentPageToken, I can use that to obtain the prevPageToken from the hash. 
 Of course, this whole process would be greatly simplified if I could just 
get the currentPageToken from the API.  That's why I asked if that was 
possible.

I must admit that I can't imagine what the "internal implementation 
reasons" could possible be that would cause Google to stop providing the 
prevPageToken.  It's very conspicuous by its absence from the API and that 
absence goes a long way towards undermining the overall utility of the API. 
 I certainly hope that this whole thing isn't just some big 
misunderstanding and we're jumping through all these hoops for no reason.

Thanks to all.

           ... doug
>
>  

-- 
You received this message because you are subscribed to the Google Groups "Blogger Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/groups/opt_out.