Changes for page Base64 encoding
Last modified by Danniar Firdausy on 2024/09/17 21:22
From version 19.3
edited by Danniar Firdausy
on 2024/09/17 21:19
on 2024/09/17 21:19
Change comment:
There is no comment for this version
To version 19.4
edited by Danniar Firdausy
on 2024/09/17 21:22
on 2024/09/17 21:22
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -47,10 +47,10 @@ 47 47 48 48 Essential characteristics of this functionality are: 49 49 50 -* Encoding (and decoding) ofbase64 stringstakeup additionalmemory(up to 33%)51 -* Separateintegrationfor the base64 strings apartfrommetadata is advisable52 -* The component i neMagizneeds a base64 encoded string as input53 -* Multiple times encoding and decoding in the same integration is **not** advisable50 +* Encoding (and decoding) base64 strings can increase memory usage by up to 33%. Plan your integrations accordingly to avoid performance issues. 51 +* It's advisable to keep base64 strings and metadata in separate integrations to prevent potential complications. 52 +* The eMagiz component used for this process requires a base64 decoded string as input. 53 +* Encoding and decoding multiple times in the same integration is **not** advisable. 54 54 55 55 == 5. Suggested Additional Readings == 56 56