[VOTE] GenericURI, HttpURL and HttpsURL API changes

[Sung-Gu <jericho at apache.org>]

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

----- Original Message ----- 
From: "Sung-Gu" <je...@contela.com>
To: "Slide Developers Mailing List" <sl...@jakarta.apache.org>
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
> 
> 

Re: [VOTE] GenericURI, HttpURL and HttpsURL API changes

[Sung-Gu <jericho at apache.org>]

FYI:

Implementation features:
- It supports LOGICAL character encoding and escaping.
   Platform string -> UCS -> UTF-8 and UTF-8 -> UCS -> Platform string
   (It's distinguished by other computational encoding and escaping utilities)
- It support various useful methods.
- Both parts in the document and communication are being useful.... 
   (Currently, it needs a fix a bit... I think )
- Fixs a previous potential bug as an ability to parse the whole components of a URI.
  (You have to notice that URL encoding and URI encoding are diffrent.... 
   Becuase the safe characters in URL encoding aren't used in URI encoding any more...
   And more we can also consider of another case called MIME-type encoding....)

Actually, the simplest and easier way to use character encoding and escaping is 
to use UTF-8 for protocol and document.  However, you will find that is not a 
necessary and sufficient codition...  Probably, you aleady know of this situation or
you can refer to RFCs and examples related to this...  So I skip this part... 

This explanation is basic for your awareness... 

I'm not in a hurry to adopt it...   So I'll wait and see when...
Probably along with test cases, it will be helpful, you guys...
(I'm afraid that I wouln't hava enough time to make them though... :(  )
When the time arrives at its need, let me have your interest...   ;)

Sung-Gu

 
> 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

The correction will be... 
4. Allow the arguments and some changes in WebdavResource,
WebdavFile and  WebdavSystemView classes

> >          [ ] +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
> > 
> > 
>