Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • 1
    +1 for the sane way to do it. Keeps the Prev/Next links 'clean' too. Commented Dec 28, 2011 at 18:51
  • 4
    A cool URL never changes. "myservice.com/photos/123/next" might point to different pictures depending on filter settings or user authorizations or day of week or phase of moon. Commented Dec 28, 2011 at 18:54
  • But it does change. If I remove photos or add new photos, there will be a different "next" photo. Commented Dec 28, 2011 at 19:22
  • 3
    There will be a different value associated with "next" in the JSON reply. The URL for a given photo never changes. You don't want to have "myservice.com/photos/123/next" and ""myservice.com/photos/345" BOTH point to the same photo. You want "myservice.com/photos/345" to be the one, only and unchanging for photo 345. Since "myservice.com/photos/123/next" is always changing, you simply do not want to ever use it. Commented Dec 28, 2011 at 19:39
  • I'm thinking that you're right. This was the original path that I went down. I was using a LinkedListNode<T> in the middle tier to generate the data. Everything was nice until I tried to serialize my LinkedListNode and . . . recursion blowup. /next seems like such a nice solution from the middle tier point of view, but alas, it does violate the Thou Shalt Have One Url And Only One Url Commandment. Commented Dec 28, 2011 at 19:58