I hope anyone can share his experience or thoughts about the use of datastore cursors in URLs that are to be crawled by search engines.
Scenario: I have a page with news items in reverse chronological order (most recent on top). The data for the page is obtained by a query and the current cursor is also returned and embedded in the "Next Page" link. So when the user clicks "Next Page", the cursor is passed back to the server and the query returns the next X results and so on. Now my question is whether this design where the cursors are embedded in the "page URL" plays nicely with Search Engines that would remember the link and the content in the page. If a user hits a URL from a search engine that contains the cursor as a parameter, possibly months later - would the query&cursor still return the same content? (assuming entries are not removed from the datastore, but newer stories are constantly added to the "top" of query). Anyone sees any issues with this approach? Thanks, Michael -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
