Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any chances of exposing Shell session details to VertxCommand extensions ? #15

Open
ramukima opened this issue Jul 25, 2014 · 1 comment

Comments

@ramukima
Copy link

For example, say I have two commands A.a and B.b. When A.a is run it initializes a map entry in vert.x shared data. When B.b is run, it fetches that data and uses it to perform the operation. Now, in order to make the shared-data not accessible to 'all sessions' to the shell, but within a given session... the session id for the shell may be required. Other alternative could be to build such capability outside the core of this module, which may seem like a hack.

@vietj
Copy link
Contributor

vietj commented Jul 26, 2014

you can store objects in current session by doing in a command:

context.session["foo"] = "bar";

please read http://www.crashub.org/1.3/reference.html#command_context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants