Changes for page Base64 encoding

Summary

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

Details

Page properties

Author

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

Default language

...	...	@@ -1,1 +1,0 @@
1		-en

Content

...	...	@@ -1,9 +1,15 @@
1	1	{{container}}
2	2	{{container layoutStyle="columns"}}
3		-(((Most of the time, you can use the standard tooling of eMagiz to manipulate the data so that it makes sense for the (external) party that receives the data. However, sometimes there are cases in which you need a little bit of extra complexity. This microlearning will explain one of those more complex scenarios. In this microlearning, we will learn how to use base64 encoding on your (input) message. This functionality is beneficial when the message is not encoded, but you need to send the data encoded to the external party.
	3	+(((
4	4
5		-Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6	6
	6	+Most of the time, you can use the standard tooling of eMagiz to manipulate the data so that it makes sense for the (external) party that receives the data. However, sometimes there are cases in which you need a little bit of extra complexity. This microlearning will explain one of those more complex scenarios. In this microlearning, we will learn how to use base64 encoding on your (input) message. This functionality is beneficial when the message is not encoded, but you need to send the data encoded to the external party.
	7	+
	8	+Should you have any questions, please get in touch with academy@emagiz.com.
	9	+
	10	+* Last update: August 26th, 2021
	11	+* Required reading time: 5 minutes
	12	+
7	7	== 1. Prerequisites ==
8	8
9	9	* Basic knowledge of the eMagiz platform
...	...	@@ -18,8 +18,10 @@
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 decoding in the same integration is **not** advisable
	27	+* Multiple times encoding and encoding in the same integration is **not** advisable
22	22
	29	+
	30	+
23	23	== 3. Base64 encoding ==
24	24
25	25	Most of the time, you can use the standard tooling of eMagiz to manipulate the data so that it makes sense for the (external) party that receives the data. However, sometimes there are cases in which you need a little bit of extra complexity. This microlearning will explain one of those more complex scenarios. In this microlearning, we will learn how to use base64 encoding on your (input) message. This functionality is beneficial when the message is not encoded, but you need to send the data encoded to the external party.
...	...	@@ -29,9 +29,9 @@
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 decoding in the same integration is **not** advisable
	40	+* Multiple times encoding and encoding in the same integration is **not** advisable
33	33
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.
	42	+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). Luckily for us, eMagiz will do all the heavy lifting, and we do not have to take out pen and paper.
35	35
36	36	In the remainder of this microlearning, we will look at how you could implement this logic within the eMagiz tooling.
37	37
...	...	@@ -61,20 +61,24 @@
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 decoding in the same integration is **not** advisable
	72	+* Multiple times encoding and encoding in the same integration is **not** advisable
65	65
	74	+
	75	+
66	66	== 6. 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		-* [[Encode Algorithm>>https://base64.guru/learn/base64-algorithm/encode||target="blank"]]
71		-* [[Base64 Encoding Online>>https://www.base64encode.org/||target="blank"]]
	80	+* https://base64.guru/learn/base64-algorithm/encode
	81	+* https://www.base64encode.org/
72	72
73	73	== 7. Silent demonstration video ==
74	74
75	75	This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
76	76
77		-{{video attachment="intermediate-data-handling-base64-encode.mp4" reference="Main.Videos.Microlearning.WebHome"/}})))
	87	+{{video attachment="intermediate-data-handling-base64-encode.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
	88	+
	89	+)))
78	78
79	79	((({{toc/}}))){{/container}}
80	80	{{/container}}