On Feb 24, 2011, at 11:18 AM, Mike Orr wrote: > Or rather, it would solve the "/index?page=2" problem. It wouldn't > solve the "/index/page/2" problem, which requires knowledge of a > specific router.
Yea, I can't say I'm really a fan of that. The whole "url's shouldn't change", and here's an arbitrary changing page as /2 will likely change. And really, its a query parameter that you want the second page... so it does seem logical that it'd be the URL's query param... at which point passing in the WebOb request would be sufficient to get the current location *and* generate the appropriate link to the next page. As for handling offset vs using a last key, it might make more sense to make a better API for the object passed in then the sequence slice operation I had imagined earlier. Cheers, Ben -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
