RE: Moving Base64 in HttpClient to commons-codec

2003-02-03 Thread O'brien, Tim
43 M 847-863-7045 > -Original Message- > From: Jeffrey Dever [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 03, 2003 2:28 PM > To: O'brien, Tim > Cc: 'Commons HttpClient Project' > Subject: Re: Moving Base64 in HttpClient to commons-codec > >

Re: Moving Base64 in HttpClient to commons-codec

2003-02-03 Thread Jeffrey Dever
PROTECTED] Subject: Re: Moving Base64 in HttpClient to commons-codec I saw that bug report and made Tim aware that xml-rpc also had an implementation. They all appear to be based on the same one that was forked and diverged over time. All I'm asking for is one authoritive place in common

Re: Moving Base64 in HttpClient to commons-codec

2003-02-03 Thread Jeffrey Dever
I saw that bug report and made Tim aware that xml-rpc also had an implementation. They all appear to be based on the same one that was forked and diverged over time. All I'm asking for is one authoritive place in commons to get Base64 functionality. Any fixes that have gone into the forked

Re: Moving Base64 in HttpClient to commons-codec

2003-02-03 Thread Ryan Hoegg
Hi Jandalf, I am not currently subscribed to Commons Dev, although I imagine I need to resubscribe sometime soon. Martin Redington just checked HttpClient's version of Base64.java, and it still has the problems in Bug 9931. We have also made some performance improvements as you will see in th

Moving Base64 in HttpClient to commons-codec

2003-02-03 Thread Jeffrey Dever
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