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

Write a Cassovary shell #212

Open
lintool opened this issue May 24, 2016 · 1 comment
Open

Write a Cassovary shell #212

lintool opened this issue May 24, 2016 · 1 comment

Comments

@lintool
Copy link

lintool commented May 24, 2016

Just like there's a Spark shell for interactively playing around, we should write a Cassovary shell that support interactive manipulation of the graphs. I've started prototyping something in my clone, under repl branch.

Better yet, instead of the current server, we should have a backend server process that loads a potentially large graph, and multiple frontend shells can connect to it and access the graph. We could use the same mechanism that Spark uses for serializing closures for execution on the backend.

Thoughts?

@pankajgupta
Copy link
Contributor

Yep that will be awesome. Memory map work done by Peter makes it easier to
load large graphs too...

On Tuesday 24 May 2016, Jimmy Lin [email protected] wrote:

Just like there's a Spark shell for interactively playing around, we
should write a Cassovary shell that support interactive manipulation of the
graphs. I've started prototyping something in my clone, under repl branch.

Better yet, instead of the current server, we should have a backend server
process that loads a potentially large graph, and multiple frontend shells
can connect to it and access the graph. We could use the same mechanism
that Spark uses for serializing closures for execution on the backend.

Thoughts?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#212

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