[
https://issues.apache.org/jira/browse/TINKERPOP-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752672#comment-16752672
]
Dominik Franek commented on TINKERPOP-2143:
-------------------------------------------
I can give you a typical use case:
Gremlin-server is running as the backend providing Graph access to the
underlying datastore (e.g. hadoop, neo4j, arangoDB...).
Gremlin-javascript can be used in the front-end application (running in the
browser) to connect to Gremlin-server. Thus the UI can display easily (using
Gremlin DSL) the data from graph datastore. So the gremlin-javascript is no
longer used as server-side component, but rather client-side, providing the
possibility to search in graph, build dynamic queries etc...
(this is what we are currently implementing, UI modules where a user will be
able to create graph queries just by UI components, without knowing the Gremlin
language. At the beginning not all feaures of gremlin language will have UI
component, as it is quire complex).
This is an just a mockup of the UI editor... And that is why Gremlin-javascript
will need to run in browser
!query-editor.jpg! )
> JavaScript GLV: Support browsers
> --------------------------------
>
> Key: TINKERPOP-2143
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2143
> Project: TinkerPop
> Issue Type: Improvement
> Components: javascript
> Reporter: Jorge Bay
> Priority: Minor
> Attachments: query-editor.jpg
>
>
> Currently the JavaScript GLV is designed to work on Node.js runtime.
> We could consider supporting browser runtimes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
