|
Post by JiangJiang on Feb 6, 2018 11:41:52 GMT
Hi,
I have a question about mentioned in Redfish DSP0266 v1.4.0 Chapter 6.4.4.5. Create (POST) , said as below
• Submitting a POST request to a Resource Collection is equivalent to submitting the same
request to the Members property of that Resource Collection.
If it means user can POST a new resource to the URI which is collection URI appended with "/Members" ? Or could you explain it more detail for me? Thanks.
|
|
|
Post by mraineri on Feb 6, 2018 18:26:46 GMT
You are correct. For example, let's say the SessionCollection is found at /redfish/v1/SessionService/Sessions. A client can POST to either /redfish/v1/SessionService/Sessions or /redfish/v1/SessionService/Sessions/Members, and the effect would be the same.
|
|
|
Post by JiangJiang on Feb 7, 2018 2:58:30 GMT
Hi,
Thank you so much for responding to my question. I have one more question for establishing a session login, in Redfish DSP0266 1.4.0 Chapter 9.2.4.2 Redfish login sessions, said as below
--------------------------------------------------------------------------------------------------------------------- The URI used for session management is specified in the Session Service. The URI for establishing a session can be found in the SessionService's Session property or in the Service Root's Links Property under the Sessions property. Both URIs shall be the same.
{ "SessionService": { "@odata.id": "/redfish/v1/SessionService" }, "Links": { "Sessions": { "@odata.id": "/redfish/v1/SessionService/Sessions" } }, ... } ---------------------------------------------------------------------------------------------------------------------
According to above description, I think the URI for creating a session is specified and must be equal to "/redfish/v1/SessionService/Sessions". Is that right? Since that, in this case shall we allow client POST to /redfish/v1/SessionService/Sessions/Members?
Thanks.
|
|
|
Post by mraineri on Feb 7, 2018 13:49:13 GMT
Yes, that's also correct.
The key thing being highlighted in section 9.2.4.2 is ensuring in the Session Collection URI is the same whether you perform a GET on the Service Root or a GET on the Session Service. Since by definition the Session Collection has a "Members" property, it's valid for a client to POST to /redfish/v1/SessionService/Sessions/Members.
|
|
|
Post by AMI_Mani on Jan 6, 2023 17:13:31 GMT
Do we need to support for posting to members attribute as mandatory? Since we can see the URI as Sessions and User can post to Sessions URI based on SessionService Get response
Links": {
"Sessions": {
"@odata.id": "/redfish/v1/SessionService/Sessions"
} Unable to see post to members in json schema, csdl file and would like to know use case of posting to members in collection resource
CSDL definition <Annotation Term="Capabilities.InsertRestrictions"> <Record> <PropertyValue Property="Insertable" Bool="true"/> <Annotation Term="OData.Description" String="New sessions can be established through a POST to the session collection."/> </Record> </Annotation> JSON defintion "deletable": false, "insertable": true, "updatable": false, "uris": [ "/redfish/v1/SessionService/Sessions" ]
Please explain to understand for supporting this based on Specification
Thanks, Mani
|
|
|
Post by jautor on Jan 6, 2023 18:03:36 GMT
Yes, for all resource collections that alternative POST to "Members" is required by the specification.
Jeff
|
|
|
Post by AMI_Mani on Jan 6, 2023 19:08:15 GMT
Thanks Jeff for the reply. In this case can we add this URI also to json, csdl files to be more clear
Mani
|
|