3 ms·
URL Parameters ≠ RPC The resource is the whole string between the domain and the fragment identifier. '/' is no different from '?' or '&' — it's all the same o
by blasdel 17y ago
URL Parameters ≠ RPC
The resource is the whole string between the domain and the fragment identifier. '/' is no different from '?' or '&' — it's all the same once you drop your false-REST preconceptions.
The HTML spec does define a standard for concatenating the name-value pairs from form elements onto target attributes for use in GET requests, but that doesn't reify it into the definition of HTTP, much less the definition of REST.
- m0th87 17y agoExcept the use of parameters for resource identification both breaks REST and isn't SEO-friendly. Forms somewhat break this for GET submissions, but do at least adhere for POST.