The nut shell being: i'm totally on board with Ryan's simple URL scheme,
having a single RequestParser/SolrRequestBuilder, going with an entirely
"inspection" based approach for deciding where the streams come from, and
leaving all mention of parsers or "stream.type" out of the URL.
(because i have a good idea of how to support it in a backwards campatible
way *later*)
Great! I just posted an update to SOLR-104 that I hope will make you happy.
It moved the various request parsing methods into distinct classes
that could easily be pluggable if that is necessary. As written, It
supports stream.type="raw|multipart|simple|standard" We can comment
that out and use 'standard' for everything as a first pass.
I added configuation to solrconfig.xml:
<requestParsers enableRemoteStreaming="true"
multipartUploadLimitInKB="2048" />
I removed LegacySelectServlet and added an explicit check in the
DispatchFilter for paths starting with "/select" This seems like a
better idea as the logic and expected results are identical.
If i'm following our discussion correctly, I *think* this takes care
of all the major issues we have.
