Loading ...
Sorry, an error occurred while loading the content.

4647Re: [rest-discuss] typical message protocols and more

Expand Messages
  • S. Mike Dierken
    Nov 1, 2004
    • 0 Attachment
      > REST applications typically use
      > * HTTP as the application protocol
      Yes.
      > * URLs as resource identifiers
      Yes.

      > * HTML form POSTs or XML as the request message protocol
      When transferring state to the server (POST, PUT) data is often sent as
      name/value pairs (encoded per the application/x-www-urlencoded definition).
      There are also file uploads where the server accepts multipart/form-data -
      each part has a content type associated. Of course, it's quite common to
      just directly POST or PUT the binary content of the data being transferred.

      > * HTML or XML as the response message protocol
      Perhaps in sheer numbers of resources, HTML, CSS, GIF, JavaScript, etc. are
      fairly popular content-types when retrieving representations of resources.
      RSS/Atom is getting more popular, but that could just be due to poor
      caching... (that's sort of a joke...)
    • Show all 12 messages in this topic