Changes for page HTTP Resources

Summary

• Page properties (4 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,0 @@
1		-HTTP Resource (Paths)

Parent

...	...	@@ -1,1 +1,0 @@
1		-WebHome

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.ebakker

Content

...	...	@@ -1,4 +1,6 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
	2	+= HTTP Resource (Paths) =
	3	+
2	2	In this microlearning, we will focus on learning about HTTP Resource (Paths).
3	3	A crucial part of setting up your (API) Gateway with the help of RESTful services is knowing to which resources (i.e. Order, Client, Employee) you want to give external parties access via your (API) Gateway.
4	4
...	...	@@ -33,6 +33,8 @@
33	33	A list of best practices can be found here:
34	34	https://restfulapi.net/resource-naming/
35	35
	38	+
	39	+
36	36	== 3. HTTP Resource (Paths) ==
37	37
38	38	This microlearning focuses on the theoretical part of HTTP Resources regardless of a specific implementation in eMagiz. In the microlearnings that will come, we will use this theoretical knowledge when we configure our API Gateway further.
...	...	@@ -56,6 +56,8 @@
56	56	In the following microlearning on HTTP Operations, we will bring the HTTP Resource (Paths) together with the HTTP Operations.
57	57	That combination is the basis for any integration that runs via the API Gateway.
58	58
	63	+
	64	+
59	59	== 4. Assignment ==
60	60
61	61	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.
...	...	@@ -67,6 +67,8 @@
67	67	* Determine usability of what is provided to you
68	68	* Take action based on that analysis
69	69
	76	+
	77	+
70	70	== 6. Suggested Additional Readings ==
71	71
72	72	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: