[ http://issues.apache.org/jira/browse/SOLR-7?page=comments#action_12373427 ]
Hoss Man commented on SOLR-7: ----------------------------- I remember being slightly anoyed by this at one point, and thinking it would be really easy to refactor the code into two seperate servlets bound to the seperate paths -- but then i realized the init method for hte servlet is what makes the core, and I wasn't motivated enough to make a choice of how to deal with that. The simplest approach would probably be to have a QueryServlet bound to /select that is in charge of initializing the core, and an UpdateServlet bound to /update ... since arguably there are more use cases where you might want to query a port without ever updating it then there are to updating a port without ever querying it. Of course, a seperate servlet/filter could be created to manage the core, it doesn't really matter that much > can't post queries > ------------------ > > Key: SOLR-7 > URL: http://issues.apache.org/jira/browse/SOLR-7 > Project: Solr > Type: Bug > Reporter: Yonik Seeley > Priority: Minor > > One can't currently post a query (must be an http-get). > The same servlet handles /update and /select, and the doPost method always > treats the request as an update. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
