|
Post by patrick on Nov 27, 2017 23:58:47 GMT
Hi, I am starting to learn the Redfish schema and will start working on a client soon. I see there are two emulators in the DMTF Github section that can serve static data from a mockup: Redfish-Mockup-Server and Redfish-Interface-Emulator.
What is the difference between these two, and why should I use one over the other?
Thanks, Patrick
|
|
|
Post by mraineri on Nov 28, 2017 21:04:57 GMT
The Mockup Server only supports GET requests, but allows you to quickly build up JSON documents and have the service provide them to a client. It's better for a proof of concept for how a client can traverse a service and read all of its data.
The Interface Emulator supports GET, PATCH, and POST requests, so it's possible to modify the data on the service. However, the Interface Emulator must be coded for the different resource types in order to support this, so it takes more time to incorporate new resource types into this tool.
As a starting point, I think the Mockup Server will be the most useful as a learning aid since it'll allow you to take the various mockup packages we have and apply them to the service. The Interface Emulator will be more useful once you need the client to modify a live resource via PATCH, create new resources via POST, or perform actions.
|
|
|
Post by patrick on Nov 30, 2017 16:41:04 GMT
Awesome, thanks for the detailed answer!
|
|