Skip to main content
Tweeted twitter.com/#!/StackProgrammer/status/581626443639185409
added 176 characters in body
Source Link

I have been in the process of generating documentation for an upcoming project. One of the features of the data available in this project is that it will be revisioned (or at least large parts of it will be).

I came across the (as I understand it, very new) "Accept-Datetime" HTTP header. This looks absolutely perfect for enabling access to revisioned data using existing interfaces.

My question is this. Which return type should be used for:

  1. A date received that is before the initial data date (I am thinking maybe 404 with body error description)?
  2. Data that is requested using the header, but that does not support versioning (This is the really sticky one for me. Not sure whether an error, or just the normal data is better)

Edit: For the moment, in the second case, I am tentatively putting code 406 - Not Accepted

I have been in the process of generating documentation for an upcoming project. One of the features of the data available in this project is that it will be revisioned (or at least large parts of it will be).

I came across the (as I understand it, very new) "Accept-Datetime" HTTP header. This looks absolutely perfect for enabling access to revisioned data using existing interfaces.

My question is this. Which return type should be used for:

  1. A date received that is before the initial data date (I am thinking maybe 404 with body error description)?
  2. Data that is requested using the header, but that does not support versioning (This is the really sticky one for me. Not sure whether an error, or just the normal data is better)

I have been in the process of generating documentation for an upcoming project. One of the features of the data available in this project is that it will be revisioned (or at least large parts of it will be).

I came across the (as I understand it, very new) "Accept-Datetime" HTTP header. This looks absolutely perfect for enabling access to revisioned data using existing interfaces.

My question is this. Which return type should be used for:

  1. A date received that is before the initial data date (I am thinking maybe 404 with body error description)?
  2. Data that is requested using the header, but that does not support versioning (This is the really sticky one for me. Not sure whether an error, or just the normal data is better)

Edit: For the moment, in the second case, I am tentatively putting code 406 - Not Accepted

deleted 76 characters in body
Source Link
user7007
user7007

I have been in the process of generating documentation for an upcoming project. One of the features of the data available in this project is that it will be revisioned (or at least large parts of it will be).

I came across the (as I understand it, very new) "Accept-Datetime" HTTP header. This looks absolutely perfect for enabling access to revisioned data using existing interfaces.

My question is this. Which return type should be used for:

  1. A date received that is before the initial data date (I am thinking maybe 404 with body error description)?
  2. Data that is requested using the header, but that does not support versioning (This is the really sticky one for me. Not sure whether an error, or just the normal data is better)

It would be really great if someone has some insight into this.

Thanks!

I have been in the process of generating documentation for an upcoming project. One of the features of the data available in this project is that it will be revisioned (or at least large parts of it will be).

I came across the (as I understand it, very new) "Accept-Datetime" HTTP header. This looks absolutely perfect for enabling access to revisioned data using existing interfaces.

My question is this. Which return type should be used for:

  1. A date received that is before the initial data date (I am thinking maybe 404 with body error description)?
  2. Data that is requested using the header, but that does not support versioning (This is the really sticky one for me. Not sure whether an error, or just the normal data is better)

It would be really great if someone has some insight into this.

Thanks!

I have been in the process of generating documentation for an upcoming project. One of the features of the data available in this project is that it will be revisioned (or at least large parts of it will be).

I came across the (as I understand it, very new) "Accept-Datetime" HTTP header. This looks absolutely perfect for enabling access to revisioned data using existing interfaces.

My question is this. Which return type should be used for:

  1. A date received that is before the initial data date (I am thinking maybe 404 with body error description)?
  2. Data that is requested using the header, but that does not support versioning (This is the really sticky one for me. Not sure whether an error, or just the normal data is better)
Source Link

Web revisioning and the Accept-Datetime header

I have been in the process of generating documentation for an upcoming project. One of the features of the data available in this project is that it will be revisioned (or at least large parts of it will be).

I came across the (as I understand it, very new) "Accept-Datetime" HTTP header. This looks absolutely perfect for enabling access to revisioned data using existing interfaces.

My question is this. Which return type should be used for:

  1. A date received that is before the initial data date (I am thinking maybe 404 with body error description)?
  2. Data that is requested using the header, but that does not support versioning (This is the really sticky one for me. Not sure whether an error, or just the normal data is better)

It would be really great if someone has some insight into this.

Thanks!