Re: Re: prevPageToken problem

I'm curious how you perceive how the index could get "screwed up". Each
page token is completely standalone and represents a chunk of your blog
post history. As long as you keep them in order, they will continue to work
correctly. One approach is a push/pop stack, (aka a LIFO
queue<http://en.wikipedia.org/wiki/LIFO_(computing)>).
There are some complexities around how to store and manage this in the face
of page reloads, but I'm guessing most people these days implement single
page AJAX apps with
pushState<https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Manipulating_the_browser_history>for
manipulating browser history anyways.


On Sat, Feb 1, 2014 at 9:01 AM, Doug Jolley <[email protected]> wrote:

> >Don't really understand why you need anything so complicated??
> > as long as the index is updated correctly
>
> And therein lies the reason.  I'm nervous about the index getting screwed
> up.  I see the hash approach as being much more robust albeit more
> complicated.
>
>          ... 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.
>



-- 

Brett Morgan | Developer Relations Engineer, Google Maps |
[email protected] | profiles.google.com/brettmorgan

-- 
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.