Github user jorgebay commented on the issue:
https://github.com/apache/tinkerpop/pull/478
I like the bottom-up approach and a really quick turnaround!
Regarding the final API, given that it's an async flow designed for remote
operations (request/response), it would be nice to define clear boundaries,
making it easier to understand for the user what causes a remote execution.
Instead an all-purpose `promise()` API, it would be nice to have a
`toListAsync()` that returns a collection of
`Vertex`/`Edge`/`Path`/...disconnected elements instead of a `RemoteTraversal`.
Similar to `toListAsync()` we could expose an async method to get a single
result, something like `firstAsync()` or `oneAsync()`, that returns the
Vertices.
---
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.
---
