Also consider that I expect Solr to support the XMLQueryParser at
some point in the near future, which would be POSTed in a body for a
search request. Being RESTful is something I strive for all too
often myself, and using HTTP verbs appropriately. But pragmatically
speaking, a POST to Solr is not a big deal. Solr is designed to be
hidden and not crawled anyway, so whatever front-end would have the
responsibility for dealing with how the world sees the search interface.
Erik
On Jan 19, 2007, at 9:16 PM, Yonik Seeley wrote:
On 1/19/07, Brian Lucas <[EMAIL PROTECTED]> wrote:
Walter Underwood wrote:
> Use GET unless it really, really, really doesn't work. POST is
> the wrong HTTP semantic for fetching information. Long query
> strings are not a good enough reason. HTTP puts no limit on the
> length of a URL.
>
Walter, while your above statement may be true, some java app
servers have
an issue with the length of URLs and truncate after a certain
point. I ran
into this issue back in April.
Yep, and given that even Apache has limits (which most people use to
front dynamic content), using really large URLs is asking for trouble.
http://www.boutell.com/newfaq/misc/urllength.html
-Yonik
