to our constraint set for REST comes from the code-on-demand style of Section 3.5.3 (Figure 5-8). REST allows client functionality to be extended by downloading and executing code in the form of applets or scripts. This simplifies clients by reducing the number of features required to be pre- implemented. Allowing features to be downloaded after deployment improves system extensibility. However, it also reduces visibility, and thus is only an optional constraint within REST. http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_7
is used to perform a retrieval action on the identified resource, the optional fragment identifier, separated from the URI by a crosshatch (“#”) character, consists of additional reference information to be interpreted by the user agent after the retrieval action has been successfully completed. As such, it is not part of a URI, but is often used in conjunction with a URI.” URI Specification, August 1998
of a URI allows indirect identification of a secondary resource by reference to a primary resource and additional identifying information. The identified secondary resource may be some portion or subset of the primary resource, some view on representations of the primary resource, or some other resource defined or described by those representations. URI Specification, January 2005
holkra
kkamegawa
righttouch
.jpg){kind=avatar}
oshanqq
axelmizu
yuj1osm
bitkey
faithandbrave
tsukuha
marchin1989
fnifni
mikanichinose
fujiwara3
dougneiner
honnibal
ufuk
aleyda
paulrobertlloyd
tammielis
sergeychernyshev
addyosmani
sferik
mojombo
soudai
lara
