Databases
StackOverflow2013
Postsdbo
POREST and multiple data formats
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POREST and multiple data formats
    primarykey
    data
    text
    <p>Ok, here is the fact. StackOverflow is implemented REST-style. When you visit a specific questions/$id/ URL you get to see the question. The content is returned in HTML because it's what the browser understands.</p> <p>I have to develop my own REST service. Fact is that I have to return multiple formats for the same information. For example, the default could be HTML, but I could return also an XML or a JSON.</p> <p>Question is: what is the recommended style to achieve this ? Three choices (more from your helpful suggestions)</p> <ol> <li>option in the URL (e.g. <a href="http://example.com/questions/12345/?format=json" rel="noreferrer">http://example.com/questions/12345/?format=json</a> )</li> <li>different interface (e.g.: for json data you have <a href="http://example.com/questions/1234/json/" rel="noreferrer">http://example.com/questions/1234/json/</a> or <a href="http://example.com/json/questions/12345/" rel="noreferrer">http://example.com/json/questions/12345/</a>, for xml data you have <a href="http://example.com/questions/1234/xml/" rel="noreferrer">http://example.com/questions/1234/xml/</a> etc... you get the point)</li> <li>http header Accept: application/json</li> </ol> <p>Same is for PUT (POST) operations. If I want to submit data in different formats, I need to inform the receiver the format I am providing, so the same situation (and question) holds.</p> <p>Thanks!</p> <p><em>Edit</em>: Additional proposal is the following</p> <p>4) Specify a proper URL for each format e.g. <a href="http://example.com/questions/12345.json" rel="noreferrer">http://example.com/questions/12345.json</a> . This looks nice, but wouldn't this mean that, for consistency, we should also have <a href="http://example.com/questions/12345.html" rel="noreferrer">http://example.com/questions/12345.html</a> ? sounds so 1995... :)</p> <p>PS: I hate markdown putting an arbitrary order to the list. If I want to start with 4, I should be able to do it. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USStefano Borini
    1. USStefano Borini
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POREST and multiple data formats
      1. USNeil
      1. VTFavorite
    2. VO
      singulars
      1. POREST and multiple data formats
      1. USAndrea Fiore
      1. VTFavorite
    3. VO
      singulars
      1. POREST and multiple data formats
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSimilar question: http://stackoverflow.com/questions/381568/rest-content-type-should-it-be-based-on-extension-or-accept-header
      singulars
      1. POREST and multiple data formats
      1. USKarl Voigtland
    2. COYes, almost a duplicate, but as it stands, it is less direct than mine. Hopefully, this question will be more beneficial for googlers.
      singulars
      1. POREST and multiple data formats
      1. USStefano Borini
    3. COURI naming schemas and nested URIs have absolutely nothing to do with REST. If you can rely on modifying parts of the URI for accessing resources predictably, chances are it's merely RPC, not REST.
      singulars
      1. POREST and multiple data formats
      1. USaehlke
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload