I just had a look at the HttpClient version. I can't see much difference from the "base" Base64 code (the one that subsequently got copied into various jakarta projects), apart from some reformatting.
The httpclient version still has the whitespace and non-Base64 character issues ...
On Monday, February 3, 2003, at 05:09 PM, Ryan Hoegg wrote:
Just noticed this on the HttpClient mailing list. Looks like things are happening with Base64. We should make sure our interests are represented as well. I know very little about the "new" version of Base64 in the HttpClient package, but we should at least make sure that our problems do not resurface.
Of course, we could just ignore them and keep our own fork. (-1)
I am posting this instead of doing this because there is a risk I won't get time to look at it for a couple days.
-- Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
From: Jeffrey Dever <[EMAIL PROTECTED]>
Date: Mon Feb 3, 2003 4:53:54 PM Europe/London
To: Commons HttpClient Project <[EMAIL PROTECTED]>
Subject: Moving Base64 in HttpClient to commons-codec
Reply-To: "Commons HttpClient Project" <[EMAIL PROTECTED]>
There is a vote on the commons-dev list to use the Base64 encoder from HttpClient in the commons-codec package. If that passes we should discuss using the the new package and deprecating/removing the fork in HttpClient.
I think that this would be good for code reuse and for commons. If you are a committer, please vote as you see fit.
http://archives.apache.org/eyebrowse/ReadMsg?listName=commons- [EMAIL PROTECTED]&msgNo=23724
Jandalf.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
