Re: [codec] RE: more common classes need a home
On Tue, 4 Feb 2003, Incze Lajos wrote: In message [EMAIL PROTECTED], Hen ri Yandell writes: I'm +1 to commons-uri. What about commons-naming? That's JNDI. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [codec] RE: more common classes need a home
+1 Any timeline for raising codec out of the sandbox? O'brien, Tim wrote: Rev 1.1 of Base64 was checked in by Sander Striker about 1 year ago. It was initially from the HttpClient project. The codec Base64 class has an open bug which also should point us in the right direction: http://issues.apache.org/bugzilla/show_bug.cgi?id=16440 So, I'll make a proposal and hope for lazy consensus: Let's replace Base64 in codec with the current HttpClient version. Tim O'Brien -Original Message- From: Jeffrey Dever [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 1:04 AM To: Jakarta Commons Developers List Subject: Re: more common classes need a home *commons.codec* sounds like a good place for this class. Perhaps you could look at the various current implementations, and see if you can provide a common Base64 class attractive to everyone in Jakarta. Currently these projects (at least) have one plus your new codec package: tomcat xml-rpc slide httpclient Three cheers for code reuse! This goes into codec, which is still in Sandbox. Infact there's already a Base64 there, but I'm not sure how well it matches Slide's needs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [codec] RE: more common classes need a home
It might need a little time for Tim to get things sorted out. It's all a bit messy in there. I guess the question needs to be whether it should focus on new functionalities or wrapping up enough to goto Commons-proper. Hen On Mon, 3 Feb 2003, Jeffrey Dever wrote: +1 Any timeline for raising codec out of the sandbox? O'brien, Tim wrote: Rev 1.1 of Base64 was checked in by Sander Striker about 1 year ago. It was initially from the HttpClient project. The codec Base64 class has an open bug which also should point us in the right direction: http://issues.apache.org/bugzilla/show_bug.cgi?id=16440 So, I'll make a proposal and hope for lazy consensus: Let's replace Base64 in codec with the current HttpClient version. Tim O'Brien -Original Message- From: Jeffrey Dever [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 1:04 AM To: Jakarta Commons Developers List Subject: Re: more common classes need a home *commons.codec* sounds like a good place for this class. Perhaps you could look at the various current implementations, and see if you can provide a common Base64 class attractive to everyone in Jakarta. Currently these projects (at least) have one plus your new codec package: tomcat xml-rpc slide httpclient Three cheers for code reuse! This goes into codec, which is still in Sandbox. Infact there's already a Base64 there, but I'm not sure how well it matches Slide's needs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [codec] RE: more common classes need a home
+1 Maybe chunked transfer encoding and URL encoding would fit into this package as well somehow? Odi O'brien, Tim wrote: Rev 1.1 of Base64 was checked in by Sander Striker about 1 year ago. It was initially from the HttpClient project. The codec Base64 class has an open bug which also should point us in the right direction: http://issues.apache.org/bugzilla/show_bug.cgi?id=16440 So, I'll make a proposal and hope for lazy consensus: Let's replace Base64 in codec with the current HttpClient version. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [codec] RE: more common classes need a home
URI, URL, and URNs are very general - and used everywhere in ASF - this sounds like prime content for the Apache Commons. I don't think that [codec] is the appropriate place for UR[LIN] code, but maybe chunked transfer encoding. I think this is even more general than networks, go to the ISOC, IANA, IAB, ITU, INTA, WIPO archives: http://www.faqs.org/rfcs/index.html, and you'll probably find that URLs are used for more things than you could've imagined. Specifically, I've been taking a crack at telephony, and you've got SIP urls and TEL urls, etc... Tim O'Brien -Original Message- From: Jeffrey Dever [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:37 AM To: Jakarta Commons Developers List Subject: Re: [codec] RE: more common classes need a home Maybe chunked transfer encoding and URL encoding would fit into this package as well somehow? Both of those are very http specific. I'm trying to find a home for all the URI, URIUtil, HttpURL ... classes too, but don't think that should be codec. There were some suggestions like commons-net, but its taken. Perhaps there is enough code for their own package commons-uri. http://archives.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED] ache.orgmsgNo=23684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [codec] RE: more common classes need a home
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. Hen On Mon, 3 Feb 2003, O'brien, Tim wrote: URI, URL, and URNs are very general - and used everywhere in ASF - this sounds like prime content for the Apache Commons. I don't think that [codec] is the appropriate place for UR[LIN] code, but maybe chunked transfer encoding. I think this is even more general than networks, go to the ISOC, IANA, IAB, ITU, INTA, WIPO archives: http://www.faqs.org/rfcs/index.html, and you'll probably find that URLs are used for more things than you could've imagined. Specifically, I've been taking a crack at telephony, and you've got SIP urls and TEL urls, etc... Tim O'Brien -Original Message- From: Jeffrey Dever [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:37 AM To: Jakarta Commons Developers List Subject: Re: [codec] RE: more common classes need a home Maybe chunked transfer encoding and URL encoding would fit into this package as well somehow? Both of those are very http specific. I'm trying to find a home for all the URI, URIUtil, HttpURL ... classes too, but don't think that should be codec. There were some suggestions like commons-net, but its taken. Perhaps there is enough code for their own package commons-uri. http://archives.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED] ache.orgmsgNo=23684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [codec] RE: more common classes need a home
On Mon, Feb 03, 2003 at 10:46:23AM -0600, O'brien, Tim wrote: Rev 1.1 of Base64 was checked in by Sander Striker about 1 year ago. It was initially from the HttpClient project. The codec Base64 class has an open bug which also should point us in the right direction: http://issues.apache.org/bugzilla/show_bug.cgi?id=16440 So, I'll make a proposal and hope for lazy consensus: Let's replace Base64 in codec with the current HttpClient version. I believe that was actually Scott Sanders (sanders), not Sander Striker (striker) :) -- Scott Sanders - [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [codec] RE: more common classes need a home
My apologies, Scott, my apologies. Tim O'Brien -Original Message- From: Scott Sanders [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:58 AM To: Jakarta Commons Developers List Subject: Re: [codec] RE: more common classes need a home On Mon, Feb 03, 2003 at 10:46:23AM -0600, O'brien, Tim wrote: Rev 1.1 of Base64 was checked in by Sander Striker about 1 year ago. It was initially from the HttpClient project. The codec Base64 class has an open bug which also should point us in the right direction: http://issues.apache.org/bugzilla/show_bug.cgi?id=16440 So, I'll make a proposal and hope for lazy consensus: Let's replace Base64 in codec with the current HttpClient version. I believe that was actually Scott Sanders (sanders), not Sander Striker (striker) :) -- Scott Sanders - [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [EMAIL PROTECTED], 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
