|
|
Post by soumikghosh on Dec 15, 2016 10:21:39 GMT
This thread is to clarify and understand the doubts of the first time readers.
|
|
|
|
Post by soumikghosh on Dec 15, 2016 13:19:05 GMT
1. How HTTP redirect is used in Redfish?
2. Is ETag required to provide consistency?
3. What is the relationship between redfish services and redfish resources?
|
|
|
|
Post by soumikghosh on Jan 3, 2017 9:07:14 GMT
Metadata and schema in Redfish context - are they same?
|
|
|
|
Post by jautor on Jan 4, 2017 22:44:34 GMT
1. How HTTP redirect is used in Redfish? 2. Is ETag required to provide consistency? 3. What is the relationship between redfish services and redfish resources? 1. HTTP Redirect is required for client software using a Redfish service, as the service may use this functionality. However, the only place a redirect is expected is at the "/redfish/v1" (no trailing slash) URI, which by spec should redirect to "/redfish/v1/" (with trailing slash). Although in that specific case the specification also allows the service to just return the /redfish/v1/ resource as if the trailing slash was there... 2. ETags are only required for the ManagerAccount resources, but otherwise, they are just recommended. 3. A "Redfish Service" is any product that implements the Redfish specification - that's the software/firmware that implements the specification. The "Redfish Resources" are the JSON payloads, defined by the Redfish schema, returned by a Redfish Service. Hope that helps, Jeff |
|
|
|
Post by jautor on Jan 4, 2017 22:47:31 GMT
Metadata and schema in Redfish context - are they same? They are related, as "schema" is metadata, but not delivered in the JSON payload. There are OData 'annotations' in Redfish, which can be metadata delivered in payload. It's best to just think of the "schema" as the data definitions and details/rules for each of the properties in a particular Redfish JSON payload (a "Resource"). Jeff |
|
|
|
Post by j2hilland on Jan 9, 2017 21:13:38 GMT
A quick note on ETags - while they are "recommended" for everything other than ManagerAccount resources, they are strongly encouraged. If your implementation supports multiple users logged on simultaneously, there is a chance that there could be a condition in your clients where they update stale data. This would lead to unhappy customers of your interface. And ETags are easy to implement.
|
|
|
|
Post by andruszamojski on Feb 23, 2017 11:15:24 GMT
Hi,
I have a question regarding Select list of @odata.context property.
Let's assume implementation supports only some of properties mentioned in schema and resource has not fully flat structure e.g.:
{
"AA":3,
"BB":{
"CC":4
}
}
Should the context property mention only "AA", "BB" or should it be also "CC" ?
Is my understanding correct that @odata.context is a single property for whole resource?
|
|
