I'd be +1 on removing all of the REST references. Agree that many developers don't care about the distinction, but to those that do, misuse of the "REST" term is either misleading or tarnishes the image of the project.
-- b > On Sep 1, 2016, at 12:35, Stephen Mallette <[email protected]> wrote: > > Robert Dale brought this issue up: > > https://issues.apache.org/jira/browse/TINKERPOP-1369 > > Basically - "The "REST API" follows exactly none of the tenets of being > RESTful. Suggest renaming it to HTTP API so as to not mislead developers as > to the design of the API." > > I agree with the technical assessment, but I don't know that the average > developer will make such distinctions as easily. People will begin > wondering where "REST" went and the questions will follow. Anyway, that's > my main reluctance with this ticket. if the consensus here is to make the > naming more technically correct, then we can leave the issue open for a > change in 3.3.0, otherwise I'd like to close and get another JIRA issue off > the board. :). > > Anyone feel strongly about this issue one way or the other?
