Hello Jochen, > http://issues.apache.org/jira/browse/FILEUPLOAD-131 > [...] > I have studied the charta of the HttpComponents and find this > statement most possibly caused by the following sentence: > > Jakarta HttpComponents MUST be content agnostic. The project DOES NOT > develop components intended to produce or consume content of HTTP > messages. > > I would like to ask to rethink this opinion, at least partially:The > httpclient project provides support for creation of multipart > requests. This support is still content agnostic, apart from the fact > that a very widespread packaging mechanism is used.
The charta was not imposed upon us. We developed it, and there are good reasons for limiting the scope: - there are too few developers, they couldn't cover a wider scope anyway - there are other Apache projects, and we must not get into their turf Getting HTTP right is hard enough on it's own. Work on HttpComponents has started more than two years ago, and there is not even a first alpha of the new HttpClient 4.0. Why should we consider extending our scope in this situation? > IMO, the server side should at least support the same level that the > client side does. No way. There are standardized APIs for server-side HTTP communication, in particular the Servlet API - which is implemented in Tomcat, one of those other projects in whose turf we must not get. There are no such standardized APIs for the client side - except HttpURLConnection, which is so limited that the HttpClient project was started in the first place. > The content encoding and, in particular, the > content-transfer-encoding cannot be viewed as independent from the > HTTP protocol. Supporting typical cases like multipart/form-data > should at least be provided as a sample implementation. Multipart form-data can be used to generate files as well as HTTP message entities. Why should it be tied to the HTTP protocol? If I am not mistaken, multipart MIME messages were developed for email communication in the first place. > If you cannot agree with my opinion, I'd like to ask how you would > handle such cases like multipart parsing in your own code. What MIME > or other libraries would you use or recommend? I'd have a look at commons-fileupload and javax.mail. Obviously commons-fileupload doesn't work for you. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
