GCloudSessionManager doesn't appear to be enabled in non-compat runtimes...

[lesv]

A quick search of the repo, and I notice that gcloudSession isn't used, nor the GCloudSessionIdManager as described in Chapter 10.

Would really be good if we had a way to preserve sessions if a user needed it.

[ludoch]

Where would you want it? compat or jetty9?
For compat, we already have a session manager.

[lesv]

Yep - I'd like something for Jetty9

[lesv]

Datastore, Memecache, Cloud Bigtable (in an ideal world)

[ludoch]

So non compat, right?

On Wed, Feb 3, 2016 at 2:33 PM, Les Vogel notifications@github.com wrote:

Datastore, Memecache, Cloud Bigtable (in an ideal world)

—
Reply to this email directly or view it on GitHub
#167 (comment)
.

[lesv]

Yep -- I think we should at least offer sessions -- it's way too hard for users to modify Jetty to roll their own.

[gregw]

in the current release (9.3.7) we have a simple gcloud session manager. The next major release (9.4.x) will have the new session manager that @janbartel has been working on that will allow memecache and datastore to be used together (and should probably replace the one in compat also).

So we can activate the simple one for now. However, we need to work out how that will work if the image is run on a local docker for testing etc. should we inject an appkey for the datastore and use it remotely or should we just run the hashsession manager....??? Will assign to jan to work out the details.

[ludoch]

Let's treat it as low priority for now. Compat can be used if a customer
wants session OOB.
In 9.4.x, I would suggest we do a sample on how to enable it in the jetty
image, but it should not be on by default.

On Wed, Feb 3, 2016 at 9:56 PM, Greg Wilkins notifications@github.com
wrote:

in the current release (9.3.7) we have a simple gcloud session manager.
The next major release (9.4.x) will have the new session manager that
@janbartel https://github.com/janbartel has been working on that will
allow memecache and datastore to be used together (and should probably
replace the one in compat also).

So we can activate the simple one for now. However, we need to work out
how that will work if the image is run on a local docker for testing etc.
should we inject an appkey for the datastore and use it remotely or should
we just run the hashsession manager....??? Will assign to jan to work out
the details.

—
Reply to this email directly or view it on GitHub
#167 (comment)
.