On 3/6/06, Nathan Bubna <[EMAIL PROTECTED]> wrote: > On 3/6/06, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > > May I, however, express my (humble) opinion that some of the Commons > > [FileUpload] code may find a better home in Commons [Codec]. To me, all > > the mime/multipart parsing logic clearly belongs to [Codec]. There are > > plans to factor out all multipart encoding code from Commons > > [HttpClient] and move it to Commons [Codec] > > > > This said, Commons [FileUpload] is welcome to consider joining JHC > > i wondered if we wouldn't see a lot of discussions like this. hard > lines have always been hard to draw. is it possible to have multiple > associations? some sort of tagging system, with labels instead of > folders?
It's not important how something is implemented, what is important is what it does. Our end users (programmers) don't care that lib Foo used lib Bar. They just care what it does. When categorizing this stuff pretend you are an end user. A lib's existence is justified by how it helps it's users get work done. -- Sandy McArthur "He who dares not offend cannot be honest." - Thomas Paine --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
