[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2017-05-18 Thread spmallette
Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/450 sorry - changed this up. i created TINKERPOP-1489 branch for js work and TINKERPOP-1552 for c# work. both branches extend from tp32-glv. in this way, the GLVs are not coupled together to be

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2017-05-18 Thread jorgebay
Github user jorgebay commented on the issue: https://github.com/apache/tinkerpop/pull/450 ok thanks! I hope I'll get some time soon to work on the JavaScript GLV to leverage the new async execution introduced in TINKERPOP-1490. --- If your project is set up for it, you can reply

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2017-05-18 Thread spmallette
Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/450 I've cherry picked this PR to this branch: https://github.com/apache/tinkerpop/tree/tp32-glv and made a commit or two to get it to compile against the tp32 branch. It's in

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2016-11-11 Thread jorgebay
Github user jorgebay commented on the issue: https://github.com/apache/tinkerpop/pull/450 > Note that there is a proposal for adding async iterator to JavaScript. Nice! I wasn't aware of that, I really like the syntax! I think the destiny of `next()` for async ops is also

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2016-10-31 Thread spmallette
Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/450 I can take a shot at TINKERPOP-1490. I think we have community consensus on the approach if I remember correctly. I will work on it this week. --- If your project is set up for it, you can

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2016-10-31 Thread okram
Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/450 @jorgebay -- thanks for being patient. We have pushed off thinking about this since it wasn't going into the 3.2.3 and we were dealing with that release the last 2+ weeks. I would like to

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2016-10-31 Thread jorgebay
Github user jorgebay commented on the issue: https://github.com/apache/tinkerpop/pull/450 I've added some fixes during the past weeks. I'll try to summarize the open issues with this patch to try to unblock it: A) Currently, the javascript GLV exposes `list()` instead

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2016-10-08 Thread spmallette
Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/450 ha +1 for a promise style api - i just wrote the exact same suggestion for the java side:

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2016-10-08 Thread jbmusso
Github user jbmusso commented on the issue: https://github.com/apache/tinkerpop/pull/450 I was thinking that supporting JavaScript `Promise` could be helpful now that they’ve been part of the ES2015 and rolled out on most JS environment (browsers/Node.js). Maybe this can be

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2016-10-06 Thread jorgebay
Github user jorgebay commented on the issue: https://github.com/apache/tinkerpop/pull/450 1: I mentioned the difficulty of delivering a `RemoteConnection` implementation inside the TinkerPop repository above. 2: I commented in TINKERPOP-1490 that `async` is a reserved keyword, in

[GitHub] tinkerpop issue #450: TINKERPOP-1489 Javascript GLV

2016-10-05 Thread okram
Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/450 I just created this ticket: https://issues.apache.org/jira/browse/TINKERPOP-1490 @jorgebay -- can you review that ticket in terms of the `one()`, `list()` callback model you are using here