You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Waldhoff, Rodney" <rw...@us.britannica.com> on 2002/01/15 20:33:06 UTC
commons-encoding? commons-mime? (was RE: [HttpClient] Make Base64
public ?)
I think we should put together a proposal for an encoding/decoding library.
commons-codec? -endec? -encoding?
commons-mime suggests something slightly different to me, but I'm not sure
exactly what. Did you intend it to be "just" a container for
encoding/decoding algorithms? MIME-based packaging is probably a good idea
at least: *.text.base64,*.text.quotedprintable, etc.
There may be some overlap with the java encoding/content type stuff to
consider here as well.
- Rod
Scott Sanders wrote:
> Perhaps commons-mime or commons-encoding?
>
> > -----Original Message-----
> > From: Waldhoff, Rodney [mailto:rwaldhof@us.britannica.com]
> > Sent: Monday, January 14, 2002 7:41 AM
> > To: 'Jakarta Commons Developers List'
> > Subject: RE: [HttpClient] Make Base64 public ?
> >
> >
> > > Perhaps it would belong in commons-util?
> >
> > I'd also rather see it in some stand-alone package/component
> > than simply made public from the httpclient component. In
> > fact, I'd rather see a commons-base64 or a commons-endec
> > package then simply put it into "catch-all" commons-util.
> > I've got some other base64 related classes (for encoding and
> > decoding streams) that could easily go into that package as
> > well, and might flesh out base64 or endec into a reasonable component.
> >
> > - Rod
> >