Github user davebshow commented on the issue:
https://github.com/apache/tinkerpop/pull/478
@aholmberg I'm not sure if I follow...it seems to me that if a
`RemoteConnection` implementation returns a list (or future list ) of
`FutureTraversers`, the traversal API can still remain independent from the
transport. Even if the GLV needs to operate on the Traversers,
`asyncio.Future`, `concurrent.Future`, and `tornado.concurrent.Future` have
compatible APIs (`done`, `cancel`, `add_done_callback`, `result`, `set_result`,
`etc.`). The "specialized" handling of the future, whether it be a coroutine
that requires a `yield`, `yield from`, or `await` expression, or a
`concurrent.Future`, will in the end be handled by application code written by
the end user.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
