DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31378>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31378 Move multipart request to a new RequestEntity type ------- Additional Comments From [EMAIL PROTECTED] 2004-09-23 07:46 ------- Mike, I like this redesign a lot. But it needs to be well-documented in the guide, so that people understand how to use it. You made the MIME boundary string a param. I have a strong feeling that we should avoid that. The boundary string should not be a constant at all. It should be randomly generated on each request. Multipart-MIME is an extremely hierarchical format that can be nested deeply. So there can be more than one boundary string and we must ensure they are all unique within the same request. I know we had a request when somebody wanted to control the boundary string. We could still allow that by accepting an optional parameter in a Part constructor. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
