You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Daniel F. Savarese" <df...@savarese.org> on 2003/02/04 08:07:19 UTC

Re: [codec] RE: more common classes need a home

I tried to read to the end of the thread so far before replying.
If the feeling is that the classes will see more use distributed
separately from HttpClient, I concur with Henri's assessment below.

In message <Pi...@umbongo.flamefew.net>, Hen
ri Yandell writes:
>
>I'm +1 to commons-uri.
>
>As Tim points out, it's not just URLs, so we could even have pieces of
>code for dealing with ISBNs etc if the need arose.
>
>I don't think they really tie well to commons-io, and losing them in
>commons-net would be a mistake probably.


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


Re: [codec] RE: more common classes need a home

Posted by Henri Yandell <ba...@generationjava.com>.

On Tue, 4 Feb 2003, Incze Lajos wrote:

> > In message <Pi...@umbongo.flamefew.net>, Hen
> > ri Yandell writes:
> > >
> > >I'm +1 to commons-uri.
> > >
>
> What about commons-naming?

That's JNDI.

Hen


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


Re: [codec] RE: more common classes need a home

Posted by Incze Lajos <in...@mail.matav.hu>.
On Tue, Feb 04, 2003 at 02:07:19AM -0500, Daniel F. Savarese wrote:
> 
> I tried to read to the end of the thread so far before replying.
> If the feeling is that the classes will see more use distributed
> separately from HttpClient, I concur with Henri's assessment below.
> 
> In message <Pi...@umbongo.flamefew.net>, Hen
> ri Yandell writes:
> >
> >I'm +1 to commons-uri.
> >
> >As Tim points out, it's not just URLs, so we could even have pieces of
> >code for dealing with ISBNs etc if the need arose.
> >
> >I don't think they really tie well to commons-io, and losing them in
> >commons-net would be a mistake probably.


What about commons-naming?

incze

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