ResourceHints Class |
Namespace: net.openstack.Core.Domain
The ResourceHints type exposes the following members.
Name | Description | |
---|---|---|
ResourceHints | Initializes a new instance of the ResourceHints class |
Name | Description | |
---|---|---|
AcceptPatch |
Gets the PATCH request formats accepted by the resource for this client;
equivalent to the Accept-Patch HTTP response header.
| |
AcceptPost |
Gets the POST request formats accepted by the resource for this client.
| |
AcceptPut |
Gets the PUT request formats accepted by the resource for this client.
| |
AcceptRanges |
Gets the range-specifiers available to the client for this resource;
equivalent to the Accept-Ranges HTTP response header.
| |
Allow |
Gets the HTTP methods that the current client will be able to use to interact
with the resource; equivalent to the Allow HTTP response
header.
| |
AuthenticationRequirements |
Gets a collection of requirements for authentication using the HTTP Authentication Framework.
| |
Docs |
Gets the location for human-readable documentation for the relation type
of the resource.
| |
ExtensionData |
Gets a map of object properties which did not map to another field or property
during JSON deserialization. The keys of the map represent the property names,
and the values are JToken instances containing the parsed JSON
values.
(Inherited from ExtensibleJsonObject.) | |
Formats |
Gets the representation types that the resource produces and consumes, using the
GET and PUT methods respectively, subject to the Allow hint. The
keys of this collections are media types,
and the values are objects which have not yet been defined.
| |
Preconditions |
Gets a collection of preconditions that the resource may require for
state-changing requests (e.g., PUT, PATCH) to include a precondition,
to avoid conflicts due to concurrent updates.
| |
Prefer |
Gets the preferences supported by the resource. Note that, as per that
specification, a preference can be ignored by the server.
| |
Status |
Gets the status of the resource. Possible values for the status are
"deprecated" and "gone".
|
Hints are just that - they are not a "contract", and are to only be taken as advisory. The runtime behavior of the resource always overrides hinted information.
For example, a resource might hint that the PUT method is allowed on all "widget" resources. This means that generally, the user has the ability to PUT to a particular resource, but a specific resource could reject a PUT based upon access control or other considerations. More fine-grained information might be gathered by interacting with the resource (e.g., via a GET), or by another resource "containing" it (such as a "widgets" collection).
The current specification defines a set of common hints, based upon information that's discoverable by directly interacting with resources. A future draft will explain how to define new hints.