I'm sending this mail again...  I thinks it didn't be sent correctly...  :(

----- Original Message ----- 
From: "Sung-Gu" <[EMAIL PROTECTED]>
To: "Slide Developers Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, May 20, 2002 4:03 AM
Subject: [VOTE] GenericURI, HttpURL and HttpsURL API changes


> 
> Hi guys,
> 
> I'm working on things related to the URI problems like parsing a URI,
> character encoding and automatic and correct URI escaping.
> It helps internalization to support multi-byte encoding and escaping more
> perfect and fixs bugs related to those...
> 
> And the previous WebdavResource class only deals with HttpURL class.
> Since the GenericURI has been an abstract class, it was not realized as a
> delegated class.   So to support HttpsURL got some problem...
> 
> For other examples, even the slide client as a command-line client
> has a bug that GenericURI doesn't have the ability to parse a whole single
> URI reference string.  And some multi-bytes characters were broken...
> 
> I think a new URI class to solve those problems is almost done except for
> dealing with some exceptions properly and supporting clone that is useful
> for sub-protocols.
> 
> So I want us to make some changes related that....  here you are...
> 
> 1. Do not use the GenericURI class any more and use a URI class.
>          [ ] +1.  I agree with the change.
>          [ ] +0.  I don't care.
>          [ ] -1.  I don't agree, because:
>  
>  2. Allow the API changes of HttpURL class
>          [ ] +1.  I agree with the change.
>          [ ] +0.  I don't care.
>          [ ] -1.  I don't agree, because:
> 
> 3. Allow the API changes of HttpsURL class
>          [ ] +1.  I agree with the change.
>          [ ] +0.  I don't care.
>          [ ] -1.  I don't agree, because:
> 
> 4. Allow the argument changes of WebdavResource class
>          [ ] +1.  I agree with the change.
>          [ ] +0.  I don't care.
>          [ ] -1.  I don't agree, because:
> 
> This suggestions are only for HEAD branch...  ;)
> 
> Sung-Gu
> 
> P.S.: Let us set aside adaptting commons-httpclient supporting https for right now
> 
> 


Reply via email to