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.

Required fields*

8
  • Why does your API need to be aware of the client? Is there some reason beyond tracking who logs in? Commented Mar 25, 2014 at 15:41
  • The argument given is so the consumer doesn't have to deal with data it doesn't know how to. So the API only gives it data it can deal with. Commented Mar 25, 2014 at 15:42
  • 2
    If the consumer doesn't know how to deal with the data, it will either ignore it, or display it as raw data. That is a concern for the consumer application, not the web api. Commented Mar 25, 2014 at 15:44
  • That is pretty much my thoughts. If it gets something it doesn't know how to handle it should ignore it. Commented Mar 25, 2014 at 16:34
  • Don't web applications have to deal with the various versions of web browsers using it? So I see a precedent. Another way to handle this is for your API to support its own versioning and the client makes use of the version it knows how to handle. Commented Mar 25, 2014 at 22:19