commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sung-Gu" <jeri...@apache.org>
Subject Re: [SURVEY] Commons-URI or not? - with java.net.URI?
Date Thu, 26 Jun 2003 05:48:51 GMT
> ----- Original Message ----- 
> From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
> To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
> Sent: Wednesday, June 25, 2003 9:38 PM
> Subject: RE: [SURVEY] Commons-URI or not?
>
> Howdy,
> I think a slightly more detailed proposal is needed: one that addresses
> specifically what commons-uri would address that's missing in
> java.net.URI and related classes.

The main reason required the own URI implementations for Jakarta is
portability and extensiblity issue I guess though.  Your comment is very
reasonable... ;)

+ Portability: JDK 1.2 or later
+ Extensibility:
  - URI-based specific extensiblity for each schemes
  - New URI related specifications support

Comparison with java.net.URI on JDK 1.4 (= one issue of new URI package
functionalities) might be important also.   The current new URI package has
some features (java.net.URI does not...) like:
- URI validate parsr (URI character sequence must be escaped, how to prove
it?)
- Charset-aware URI reference container (possbily lagacy support with old?
charset fashion, not UTF-8 though )
- Both escaped & unescaped components manipulations (regarded as only
escaped in java.net.URI?)
- Escape codec utility (possbile to define correct escaped URI components
manually by developers)

On top of my head, I can summarize the above much right now.

Thank you very much,

Sung-Gu


> Yoav Shapira
> Millennium ChemInformatics
>
>
> >-----Original Message-----
> >From: Sung-Gu [mailto:jericho@apache.org]
> >Sent: Wednesday, June 25, 2003 1:10 AM
> >To: Jakarta Commons Developers List; Commons HttpClient Project
> >Subject: [SURVEY] Commons-URI or not?
> >
> >
> >Hi all,
> >
> >I suggest that jakarta-commons provides flexible URI issue
> implementations
> >as a package.
> >
> >Various applications using URI concept comes in the internet world.
> and
> >they need common mechanisms and algorithms for URI.
> >
> >For example, all internet programs will need fundamental functionalites
> of
> >URI like extensible parsing and manipulation container for URL
> reference,
> >URN and URC,  escape codec mechanism, charset tranformation
> functionality,
> >URI transformation from real world identities or URN, or other
> >transformations related to DNS or telephony...   If it would be
> prepared
> >commonly in Jakarta, we can save development powers.   So I suggest new
> >commons-uri package.
> >
> >FYI, currently the commons-httpclient is using it.
> >
> >Any comments?
> >Or any +1, -1?
> >
> >Sung-Gu
> >
> >P.S.: If the requirement is very weak, I want  to put the new package
> into
> >commons-sandbox even for a long while in my opinion...


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message