----- Original Message ----- From: "Eric Johnson" <[EMAIL PROTECTED]>
> I too am against a separate URI commons package, at least for the moment. [snip] > Anyway, to the extent that a separate URI package would make sense, if > we had a model such as the above, where most people used the one giant > JAR instead of the individual ones, the creation of a separate commons > URI project would be largely one of focus and interest, rather than an > additional dependency quagmire. I think so... ;) Thank you for clearing the current true issue. Sung-Gu > -Eric Johnson > > 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. > > > >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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]