We've been saying for some time now that Gremlin Server would not have a REST API as it typically doesn't represent the right pattern for graph access and remote Gremlin processing. I think that still holds true for many use cases, however, the composability of Netty channel pipelines and the abstractions built into Gremlin Server made the code base for creating a simple REST API akin to Rexster's Gremlin Extension (
https://github.com/tinkerpop/rexster/wiki/Gremlin-Extension) fairly straightforward.
The soon to be released M5 of TinkerPop3 will include this feature in Gremlin Server which basically allows it to be configured to expose a single REST endpoint which processes Gremlin scripts (and bindings) such that you can do:
This feature should help those trying to transition from Rexster (assuming you were using the REST Gremlin Extension) and provide support for tools like Bulbs which relied on that extension for most of its operations.
You can read more about this feature here:
Enjoy!
Stephen