indicate session timeout?

[flipside]

I've often spent several minutes constructing a graph, tested some queries, gone off and done something else, tried to run the queries again except all the nodes are gone except for 0.

Is there any way to cache the graph so I can reload it (initializing query) using the url shortener?

Alternatively, a more prominent save button could work.

[jexp]

@flipside that's the session timeout after 20 minutes. Sorry. But too many open sessions eat all the memory on the server. We will record a video showing the usage of the console. And make the buttons more obvious "share" and "toggle graph" instead of icons.

Also I just had the idea of providing a "input history log" in the share window too?
And perhaps before destroying the session, storing the current graph in the console and saving the id for a redirect? So you can continue on the next operation.

[flipside]

I figured the session was around 20 minutes, however it always caught me by surprise because there was no indication the session had reset until I tried to do something.

I completely support storing the graph in console before destroying the session, just throw up a notification with options to reload or reset.

A list of successful queries could be interesting in the share window.

[peterneubauer]

Any sketch on how that would look like (successful queries?) also, we
should rename the issue to "indicate session timeout?"

On Thu, Dec 20, 2012 at 10:53 PM, Mat Tyndall notifications@github.comwrote:

I figured the session was around 20 minutes, however it always caught me
by surprise because there was no indication the session had reset until I
tried to do something.

I completely support storing the graph in console before destroying the
session, just throw up a notification with options to reload or reset.

A list of successful queries could be interesting in the share window.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/41#issuecomment-11593778.

[flipside]

A scrollable list with checkmarks next to them (text fields like the initial cypher query would be acceptable). The default could be just to have the last query checked. If you include failed queries, you should have some sort of indicator next to them.

If your sharing a list, you could also chain the queries together on load so it executes a series of cypher queries. This would be very cool for showing the power of mutating cypher.

[akollegger]

Could you elaborate on the legitimate use case that expects an inherently
transient facility to be available for more than the time a user would
continuously stare at an unchanging screen?

On Thursday, December 20, 2012, Peter Neubauer wrote:

Any sketch on how that would look like (successful queries?) also, we
should rename the issue to "indicate session timeout?"

On Thu, Dec 20, 2012 at 10:53 PM, Mat Tyndall <notifications@github.com<javascript:_e({}, 'cvml', 'notifications@github.com');>>wrote:

I figured the session was around 20 minutes, however it always caught me
by surprise because there was no indication the session had reset until
I
tried to do something.

I completely support storing the graph in console before destroying the
session, just throw up a notification with options to reload or reset.

A list of successful queries could be interesting in the share window.

—
Reply to this email directly or view it on GitHub<
https://github.com/neo4j-contrib/rabbithole/issues/41#issuecomment-11593778>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/41#issuecomment-11604316.

[flipside]

I use the console to test queries which often involves setting up the graph. Afterwards I test out my queries and then implement them if they work. Often I need to go back and forth due to unforeseen complications. I don't keep close track of time and am often surprised when the console has reset.

A few other points:

1. It is not clear that it is transient, nowhere does it say it will only persist for 20 minutes
2. It doesn't prompt you to "save your work" before it deletes the graph, the screen doesn't change and it looks like the graph is still there.
3. The only sign that the graph is gone is that queries that reference missing nodes will fail, which is confusing and disheartening.

[freeeve]

Yeah, this has bitten me many times. My normal practice is to save the graph as a generated URL via the share button, so that I can just hit refresh to get back to where I started.