Changeset 2103 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 10/01/13 08:40:38 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r2102 r2103 1490 1490 <t> 1491 1491 The DELETE method requests that the origin server remove the association 1492 between the <x:ref>target resource</x:ref> and its current representations or 1493 implementation. In effect, this method is similar to the rm command in 1494 UNIX: it expresses a deletion operation on the URI mapping of the 1495 origin server, rather than an expectation that the information be deleted. 1496 The representations might or might not be destroyed by the origin server, 1497 and the associated storage might or might not be reclaimed, depending 1498 entirely on the nature of the resource and its implementation by the 1499 origin server (which are beyond the scope of this specification). 1492 between the <x:ref>target resource</x:ref> and its current functionality. 1493 In effect, this method is similar to the rm command in UNIX: it expresses a 1494 deletion operation on the URI mapping of the origin server, rather than an 1495 expectation that the previously associated information be deleted. 1496 </t> 1497 <t> 1498 If the target resource has one or more current representations, they might 1499 or might not be destroyed by the origin server, and the associated storage 1500 might or might not be reclaimed, depending entirely on the nature of the 1501 resource and its implementation by the origin server (which are beyond the 1502 scope of this specification). Likewise, other implementation aspects of a 1503 resource might need to be deactivated or archived as a result of a DELETE, 1504 such as database or gateway connections. In general, it is assumed that the 1505 origin server will only allow DELETE on resources for which it has a 1506 prescribed mechanism for accomplishing the deletion. 1500 1507 </t> 1501 1508 <t>
Note: See TracChangeset
for help on using the changeset viewer.