Changes for page Base64 encoding

Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -18,7 +18,7 @@
18	18	* Encoding (and decoding) of base64 strings take up additional memory (up to 33%)
19	19	* Separate integration for the base64 strings apart from metadata is advisable
20	20	* The component in eMagiz needs a base64 encoded string as input
21		-* Multiple times encoding and encoding in the same integration is **not** advisable
	21	+* Multiple times encoding and decoding in the same integration is **not** advisable
22	22
23	23	== 3. Base64 encoding ==
24	24
...	...	@@ -29,7 +29,7 @@
29	29	* Encoding (and decoding) of base64 strings take up additional memory (up to 33%)
30	30	* Separate integration for the base64 strings apart from metadata is advisable
31	31	* The component in eMagiz needs a base64 encoded string as input
32		-* Multiple times encoding and encoding in the same integration is **not** advisable
	32	+* Multiple times encoding and decoding in the same integration is **not** advisable
33	33
34	34	The Base64 encode algorithm converts the original string into a base64 encoded string. Technically, it can be said that it converts eight-bit bytes into six-bit bytes. So when you have a string of ABC, you could manually convert this to an encoded format. You can find an excellent explanation of how it works [[here>>https://base64.guru/learn/base64-algorithm/encode||target="blank"]]. Luckily for us, eMagiz will do all the heavy lifting, and we do not have to take out pen and paper.
35	35
...	...	@@ -49,32 +49,22 @@
49	49
50	50	Now that we know how to implement it, we can quickly look at possible use cases for this logic. We see this logic popping up mainly when dealing with attachments/files (i.e., pictures, pdf) within XML messages.
51	51
52		-== 4. Assignment ==
	52	+== 4. Key takeaways ==
53	53
54		-Look for places where you could use this logic to aid your integration process within your (Academy) project.
55		-This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment.
56		-
57		-== 5. Key takeaways ==
58		-
59	59	Essential characteristics of this functionality are:
60	60
61	61	* Encoding (and decoding) of base64 strings take up additional memory (up to 33%)
62	62	* Separate integration for the base64 strings apart from metadata is advisable
63	63	* The component in eMagiz needs a base64 encoded string as input
64		-* Multiple times encoding and encoding in the same integration is **not** advisable
	59	+* Multiple times encoding and decoding in the same integration is **not** advisable
65	65
66		-== 6. Suggested Additional Readings ==
	61	+== 5. Suggested Additional Readings ==
67	67
68	68	If you are interested in this topic and want more information, please read the help text provided by eMagiz and the following links:
69	69
70	70	* [[Encode Algorithm>>https://base64.guru/learn/base64-algorithm/encode||target="blank"]]
71	71	* [[Base64 Encoding Online>>https://www.base64encode.org/||target="blank"]]
	67	+)))
72	72
73		-== 7. Silent demonstration video ==
74		-
75		-This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
76		-
77		-{{video attachment="intermediate-data-handling-base64-encode.mp4" reference="Main.Videos.Microlearning.WebHome"/}})))
78		-
79	79	((({{toc/}}))){{/container}}
80	80	{{/container}}