Changes for page Base64 encoding
                  Last modified by Danniar Firdausy on 2024/09/17 21:22
              
      
      From version  16.1 
    
    
              edited by Erik Bakker
        
on 2023/01/23 09:01
     on 2023/01/23 09:01
      Change comment:
              There is no comment for this version
          
         
      To version  17.1 
    
    
              edited by Bouke Reitsma
        
on 2023/05/12 08:28
     on 2023/05/12 08:28
      Change comment:
              There is no comment for this version
          
         Summary
- 
          Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
- 
      - Author
-   ... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.BoukeReitsma 
- 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 e ncoding in the same integration is **not** advisable21 +* 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 e ncoding in the same integration is **not** advisable32 +* 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 ... ... @@ -61,7 +61,7 @@ 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 e ncoding in the same integration is **not** advisable64 +* Multiple times encoding and decoding in the same integration is **not** advisable 65 65 66 66 == 6. Suggested Additional Readings == 67 67 
 
