![]() If a call to an get Command is expected to return back the human and dog count data, then the response’s expected values would be. The expected values in a response are an array of Value Descriptor names. For practical purposes, the code is usually an HTTP status code like 200 (for good responses), 404 or 503 (examples of bad responses). ![]() Each response is made up of a code (which suggests if it is a good or error response), a description (human readable information about what is in the response), and an array of expected values. Each get should have at least one “good” response, but it may have several error responses depending on what problems or issues the Device Service may need to reply with. Responses might be “good” or “error” responses. A put is not required to have a response. A get must have at least one response object. Get and puts then have response objects (an array of response objects). Hypothetically, if the address to a Device Service was “ and the get Command had a path of “foo”, then internally, EdgeX would know to use “ to call on the get Command. ![]() The get and put each have a path which is used by EdgeX to call on the specific Command get or put at the URL address provided for the service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |