|
So you are saying that your library is going to expose both the binary
and Base64-encoded form? That means your library will provide its own
Base64 encoder/decoder?
What makes Base64 worth being part of the project, but JSON not?
On Wed, Jul 26, 2017 at 9:59 AM, jacobus erps <jacobus.erps@xxxxxxxxx>
wrote:
Serialization to binary form is most compact format.compact,
This binary form can also be represented in BASE64, which is less
but you're able for example to copy this text into a mail and send it to
somebody.
So you are saying that your library is going to expose both the binary
and Base64-encoded form? That means your library will provide its own
Base64 encoder/decoder?
What makes Base64 worth being part of the project, but JSON not?
What about
<https://github.com/RelicPackages/base64>
which seems like another distribution of
<http://www.scottklement.com/base64/>
John Y.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.