Re: prevPageToken problem
Doug Jolley <[email protected]>
| Newsgroups | gmane.comp.web.blogger.api |
|---|---|
| Message-ID | <[email protected]> |
As I understand it, the suggested "work around" is "to remember your page
tokens as you iterate". I take that to mean grab the nextPageToken and
stuff it into some sort of array or hash as one iterates. If that's
correct, I'm not exactly sure how one gets the page token associated with
the first page. The bottom line is that (IMO) "workarounds" are only good
as simple temporary patches intended to plug a gap for a short period of
time while the actual fix is being implemented. I don't see any workable
approach that is simple enough to qualify as a "workaround" for this issue.
If this bug has been known for over year and is not yet fixed, I'm not
real hopeful. That means that a major component of the API is pretty much
useless. It's really disappointing to have invested a considerable number
of hours in the development of an application only to find that it's not
going to work because of a bug in the API. I would suggest that if the bug
can't be fixed, some sort of prominent notice be inserted into the
documentation so that developers don't waste time developing around an API
feature that doesn't work.
... 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.