Comment 16 for bug 302656

Revision history for this message
mangtronix (mang) wrote :

Hmm it turns out going through our code path for /stream is pretty slow (needs to do a bunch of checks to see what the type of the item is) so I'm hesitant to do a Location redirect as I suggested in #3 above

I think I'll use Raj's suggestion and have the JS user agent append the current location using the hash mark and window.replace. This also solves the problem of sending an non-JS user agent to a URL where state is only encoded after the hash mark.

So browser-generated URLs will look like this as the user browses through the book:
http://www.archive.org/stream/aliceinwonderlan00carriala/page/23#page24

The canonical URL for this example as generated by the "share" functionality would be this:
http://www.archive.org/stream/aliceinwonderlan00carriala/page/24