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? - about starting point
Date Thu, 26 Jun 2003 04:57:37 GMT

----- Original Message ----- 
From: "Martin Cooper" <martinc@apache.org>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Cc: "Commons HttpClient Project" <commons-httpclient-dev@jakarta.apache.org>
Sent: Thursday, June 26, 2003 2:37 AM
Subject: Re: [SURVEY] Commons-URI or not?


>
>
> On Wed, 25 Jun 2003, Sung-Gu wrote:
>
> >
> > 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.
>
> If you want to do this, I would recommend starting in the sandbox. That
> way, we'll find out if it is viable as a standalone component, and, in
> particular, if a community develops around it.

Yes, I think so.   That would be the proper procudure.
At this moment, I try to ask others' needs, not simply, rather than their
interests and concerns. ;)

Thank you,

Sung-Gu


> Even though the code originates from HttpClient, I would be against a
> Commons-URI component starting out in Commons Proper, because history
> shows us that a body of code does not always develop into a viable
> component, with its own community, just because it comes from an already
> successful project.
>
> --
> Martin Cooper
>
>
> >
> > 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