[
https://issues.apache.org/jira/browse/TINKERPOP-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaunak Das updated TINKERPOP-1229:
-----------------------------------
Description:
When switching back and forth with :remote console, we have the following:
{code}
gremlin> :remote console
==>Exited remote console - all scripts will now be evaluated locally
gremlin> :remote console
==>All scripts will now be sent to Gremlin Server -
[localhost/127.0.0.1:8182]-[9672ab95-704b-4473-a1b4-1bdc84efe04a] - type
':remote console' to exit
{code}
It will help users if we can add a little more to this output:
{code}
gremlin> :remote console
==>Exited remote console - all scripts will now be evaluated locally
{code}
Perhaps, to allow the user to know how to switch in and out:
{code}
gremlin> :remote console
==>Exited remote console - all scripts will now be evaluated locally.
- type ':remote console' to evaluate all scripts on Gremlin Server -
[localhost/127.0.0.1:8182]
{code}
Also, notify the user if they are entering into a new session each time, or an
existing one (is the latter even possible? Or are sessions flushed with each
:remote console out?)
was:
When switching back and forth with :remote console, we have the following:
{code}
gremlin> :remote console
==>Exited remote console - all scripts will now be evaluated locally
gremlin> :remote console
==>All scripts will now be sent to Gremlin Server -
[localhost/127.0.0.1:8182]-[9672ab95-704b-4473-a1b4-1bdc84efe04a] - type
':remote console' to exit
{code}
It will help users if we can add a little more to this output:
{code}
gremlin> :remote console
==>Exited remote console - all scripts will now be evaluated locally
{code}
Perhaps, to allow the user to know how to switch in and out:
{code}
gremlin> :remote console
==>Exited remote console - all scripts will now be evaluated locally.
- type ':remote console' to evaluate all scripts on Gremlin Server -
[localhost/127.0.0.1:8182]-[9672ab95-704b-4473-a1b4-1bdc84efe04a]
{code}
> More Descriptive Messaging for :remote console
> ----------------------------------------------
>
> Key: TINKERPOP-1229
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1229
> Project: TinkerPop
> Issue Type: Bug
> Components: console, server
> Reporter: Shaunak Das
> Priority: Minor
>
> When switching back and forth with :remote console, we have the following:
> {code}
> gremlin> :remote console
> ==>Exited remote console - all scripts will now be evaluated locally
> gremlin> :remote console
> ==>All scripts will now be sent to Gremlin Server -
> [localhost/127.0.0.1:8182]-[9672ab95-704b-4473-a1b4-1bdc84efe04a] - type
> ':remote console' to exit
> {code}
> It will help users if we can add a little more to this output:
> {code}
> gremlin> :remote console
> ==>Exited remote console - all scripts will now be evaluated locally
> {code}
> Perhaps, to allow the user to know how to switch in and out:
> {code}
> gremlin> :remote console
> ==>Exited remote console - all scripts will now be evaluated locally.
> - type ':remote console' to evaluate all scripts on Gremlin Server -
> [localhost/127.0.0.1:8182]
> {code}
> Also, notify the user if they are entering into a new session each time, or
> an existing one (is the latter even possible? Or are sessions flushed with
> each :remote console out?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
