Skip to content

Low Hanging Fruit: Factor our Base64 Encoding/Decoding into boost/network/utils/ #287

@deanberris

Description

@deanberris

I'm filing this issue so that someone can pick it up. There's code in boost/network/protocol/http/message{hpp.ipp} that does Base64 encoding/decoding. Currently, its UNUSED anywhere in the codebase and making it easier to use and available stand-alone can be done as a simple project.

My suggestion is to move this into separate headers and implementation files (don't need to be header-only), and follow STL algorithm conventions. A good place to put this is in boost/network/utils/ beside the thread_pool.hpp implementation.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy