[ 
https://issues.apache.org/jira/browse/SOLR-15781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450693#comment-17450693
 ] 

Gus Heck commented on SOLR-15781:
---------------------------------

yeah my comment clashes with the "cosmetic" bit of this, but I noticed it 
contains an issue contemplating changing things to properly use get/put (and 
post?)... presumably in accordance with "normal" REST based usage 
([https://restfulapi.net/rest-put-vs-post/])... if we are to do that it would 
be nice to let the container call the appropriate method in a servlet rather 
than writing our own method based dispatch or filtering code

i.e. not writing code such as 
{code:java}
if ("PUT".equals(method)) { /* do stuff */ }{code}
But rather only /* do stuff */ in the doPut method. Of course we might wind up 
doing some of that if we want to return 405 - Method Not Allowed responses 
anyway... but this is why I say "consider" 

 

> Cosmetic and consistency improvements to v2 API
> -----------------------------------------------
>
>                 Key: SOLR-15781
>                 URL: https://issues.apache.org/jira/browse/SOLR-15781
>             Project: Solr
>          Issue Type: Improvement
>          Components: v2 API
>            Reporter: Jason Gerlowski
>            Priority: Major
>              Labels: V2
>
> While the v2 API is in many ways an improvement over v1 in terms of 
> readability and API best practices, it still has a lot of room for 
> improvement.  The recent "exper
> imental" designation for v2 opens the door to pursuing many of these 
> improvements. 
> This ticket is intended as an umbrella to track resolution of some of the 
> known warts in the current v2 API and some of the improvements that can be 
> made in terms of being more RESTful, etc.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to