You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by Bernd Eilers <Be...@Sun.COM> on 2002/04/26 15:33:50 UTC

deperatly searching for a committer for #3923# bugfix

Hi there !

Some time ago I supplied a bug fix for 
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3923 but nothing has 
happend so far.

Is there any chance to get that patch or a better solution into the 
current source code ?

Is there more discussion on this topic needed on this mailing list ?

Are there any plans in the slide development team to migrate to a more 
recent version of the http-commons package soon, instead of using two (!) 
different modified old ones ?

Kind regards,
Bernd Eilers



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: deperatly searching for a committer for #3923# bugfix

Posted by Sung-Gu <jericho at apache.org>.
Hi Bernd Eliers,

> ----- Original Message ----- 
> From: "Bernd Eilers" <Be...@Sun.COM>
> To: <sl...@jakarta.apache.org>
> Sent: Friday, April 26, 2002 10:33 PM
> Subject: deperatly searching for a committer for #3923# bugfix
> 
> 
> 
> Hi there !
> 
> Some time ago I supplied a bug fix for 
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3923 but nothing has 
> happend so far.
> 

I haven't had a nce to check your bug reported yet though.   :(
But I noticed that these problems related to character and escape encoding exist.
And these days I have made a class to deal with only URI. 
(I haven't had tests yet, though...  It's in the cvs repository right now)
I will apply to them some time later...  I assume.

> Is there any chance to get that patch or a better solution into the 
> current source code ?

The URI class supports not only some wrong escape encoding, but also character
encoding like multi-byte characters (Non-ASCII characters, I mean it)

> 
> Is there more discussion on this topic needed on this mailing list ?
> 
> Are there any plans in the slide development team to migrate to a more 
> recent version of the http-commons package soon, instead of using two (!) 
> different modified old ones ?

I hope so.  I'm willing to do it.   However they made some architectural changes.
In order to be applied from commons httpclient 2.0, the API compatiblity isn't sured.
As I'm assumed, Slide 2.0 will come to about 6 months later... 
So I'm waiting for the proper time to apply it.
The change of the major version means possbily the API changes for the developers.

Sung-Gu