I just posted a new patch on SOLR-104. I think it addresses most of the issues we have discussed. (Its a little difficult to know as it has been somewhat circular) I was going to reply to your points one by one, but i think that would just make the discussion more confusing then it already is!
> (i don't trust HTTP Client code -- but for the sake > of argument let's assume all clients are perfect) what happens when a > person wants to send a mim multi-part message *AS* the raw post body -- so > the RequestHandler gets it as a single ContentStream (ie: single input > stream, mime type of multipart/mixed) ? Multi-part posts will have the content-type set correctly, or it won't work. The big use-case I see is browser file upload, and they will set it correctly.
I don't see it as a big problem because we don't have to deal with legacy streams yet. No one is expecting their existing stream code to work. The only header values the SOLR-104 code relies on is 'multipart' I think that is a reasonable constraint since it has to be implemented properly for commons-file-upload to work. ryan
