Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/748
Unless I'm not thinking of something, this approach won't work for remote
traversals. When you call iterate on the client, it will serialize to bytecode.
The bytecode ends up on the server and then becomes deserialized back into a
traversal. This server traversal will not know that the client called
`iterate()` and then won't be able to also call `iterate()` on the server side
- which goes back to the optimization I mentioned in my previous comment.
---
