Skip to main content

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.

Required fields*

11
  • 1
    Assuming that it is possible for ownership to be transferred, the last approach would entail having to check if that user is still the owner of said resource. So you end up having the token plus one of the other approaches. Commented Mar 29, 2016 at 18:32
  • @MiguelvandeLaar Thanks for the response! you are correct, however in my use case ownership cannot be transferred, under any circumstances. Commented Mar 29, 2016 at 18:44
  • 2
    "a server session" Unless I'm missing something substantial, REST precludes server-side sessions. Commented Mar 29, 2016 at 18:45
  • @BarryTheHatchet - It seems like that is debate-able, there is some interesting discussion here on that: stackoverflow.com/questions/6068113/…. That solution is also around last as it makes introducing new load balanced servers fun.. Commented Mar 29, 2016 at 18:53
  • @Ashtonian: The 131-scored accepted answer to that question agrees with me ;) (as does the 223-scored followup) Commented Mar 29, 2016 at 18:54