Boost logo

Boost :

Subject: Re: [boost] base64?
From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2017-07-24 17:02:59

On Mon, Jul 24, 2017 at 9:54 AM, Roger Leigh via Boost
<boost_at_[hidden]> wrote:
> We already have base64 conversion in boost/archive/iterators/*base64*.hpp.
> It works but screws up the whitespace
> (
> It's a shame the various adapters don't work properly together; is there any
> prospect of this being fixed, or is the existing design simply too
> inflexible to make a proper base64 implementation?

I think a good base64 implementation would be an excellent subject for
GSoC or someone who wants to participate in Boost we would just have
to clearly define the things we want from it:

* Caller provided buffers
* Allocator awareness
* Flexible types of input
* Choice of alphabet
* Choice of radix?
* Option for line-widths / newlines
* Iterator based interface
* Variations such as rfc3548, rfc, 4648, modified Base64 for URL

Could be called Boost.Radix

I know such a library would be immensely useful to a higher-level
library which tries to address some of those "out-of-scope" items in
Beast. Base-64 and other radix encodings come up often in HTTP field
values and uri targets, as well as in the body of certain message

If anyone is interested I wouldn't mind getting together on Google
Hangouts with a shared document and hammering out
a prototype set of declarations, which someone else could implement.


Boost list run by bdawes at, gregod at, cpdaniel at, john at