Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/748
In reviewing this, I think Gremlin Server needs a change. When we submit a
remote traversal. Gremlin Server needs to check for `iterate()` in the bytecode
and actually call `iterate()` rather than `next()` that way the graph instance
gets the right method called on it for any additional optimization that could
occur there. Plus, if the client did call `iterate()` it's better that Gremlin
Server simply return no results - that's a big optimization. I can work on that
change and just commit it to this branch as part of this PR.
---
