On 3/6/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > On 3/6/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > > * FileUpload (active, martinc should confirm interest in moving to JWC) > > I'm not so sure about this. FileUpload has already cloned some code from > HttpClient, and could undoubtedly make use of more. Its purpose is to parse > HTTP requests. So I'm actually more inclined to move this to Jakarta HTTP > Components, assuming that HttpClient eventually morphs into that. (I thought > it had already, but I can't seem to find a JHC anywhere.)
As a programmer looking for useful code to help me with uploaded files, I'm going to look in something named Jakarta *Web* Components first. When I see Jakarta HTTP Components I think of interacting with the HTTP protocol. I know FileUpload does both, but when I'm writing an webapp I think I'm working with a *web* app first and while I am working with HTTP it is a secondary concern. -- 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]
