Skip to Content

Changes for page HTTP Resources

Last modified by Erik Bakker on 2024/08/23 10:51
From version 7.1
edited by Eva Torken
on 2023/04/20 11:33
Change comment: There is no comment for this version
To version 9.1
edited by Eva Torken
on 2023/06/08 11:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -53,23 +53,16 @@
53 53  In the following microlearning on HTTP Operations, we will bring the HTTP Resource (Paths) together with the HTTP Operations.
54 54  That combination is the basis for any integration that runs via the API Gateway.
55 55  
56 -== 4. Assignment ==
56 +== 4. Key takeaways ==
57 57  
58 -Read up on the best practices when it comes to the naming of HTTP Resource Paths and see if you can relate this to the eMagiz implementation.
59 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
60 -
61 -== 5. Key takeaways ==
62 -
63 63  * Start at the backend operation
64 64  * Determine usability of what is provided to you
65 65  * Take action based on that analysis
66 66  
67 -== 6. Suggested Additional Readings ==
62 +== 5. Suggested Additional Readings ==
68 68  
69 69  If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
70 70  
71 71  * [[REST API naming concepts>>https://restfulapi.net/resource-naming/||target="blank"]]
72 72  
73 -== 7. Silent demonstration video ==
74 -
75 -As this is a more theoretical microlearning no demonstration video is created. See you in the next microlearning.)))((({{toc/}}))){{/container}}{{/container}}
68 +)))((({{toc/}}))){{/container}}{{/container}}