Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThe bookmarking done by your agent is a local private cache for just this client on this machine, right? The cache contains a map between a string and the actual URI you'll need to re-get later. How do build the strings that become the keys in this map? Is there a general scheme? Probably not. What is the standard algorithm for using a REST service? How about: "Start with this root URI and crawl around the resource graph, using GET, OPTIONS, and HEAD, until you've located all needed resource representations, and remember to cache the ones you think you will need to get again soon."
      singulars
    2. COIs the REST community trying to standardize such an algorithm for using a REST service? Not having such a standard and not having a way to use opaque URLs (and still be able to walk the resource graph) prevent me from using REST. So I use WSDL/Soap. I sense from the reading I've done that most REST proponents don't value this ability of a machine to use a REST service automatically and quickly, as can be done with WSDL/Soap.
      singulars
    3. COThe resource aggregation idea above is a good one, but I think someone should publish it as "the best way" or one of "these five best ways" to get your resource representations out of a REST-based resource graph. If these standards exist in rigorous form somewhere, please point me to them. We need more structure and guidance in this REST craft than HTTP verbs and response codes.
      singulars
 

Querying!

 
Guidance

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