Memcached support? about scs HOT 7 CLOSED

I don't see any reason there couldn't be a memcached engine.

I'll add one when I've got time, or if you'd like to send a PR that would be very welcome!

from scs.

No worries @alexedwards. I'll take a look at doing a PR, but not sure yet. Got an initial implementation using gorilla/sessions + bradpeabody's memcached store working yesterday, so going to try with that first.

We're using Go 1.8 atm (and likely 1.9 soon), which the docs on gorilla/sessions sound like it has issues with. So, may need to investigate alternatives shortly, in which case... a PR will be created. 😉

from scs.

Co-incidentally, it's interesting your personal home page mentions data.police.uk.

That's one of the data sources I've been looking at mirroring as example data, for the project I'm implementing memcached sessions for (dbhub.io).

from scs.

Yep, myself and @rkhleics worked on data.police.uk for many years. It's a good resource.

Out of interest, what's the potential problem with gorilla/session and v1.9? I couldn't find any notes about it.

from scs.

Well, the gorilla/sessions readme seems to say that people running Go 1.7+ and not using gorilla/mux will need to add gorilla/context to their imports list, plus do some stuff with gorilla/context.ClearHandler() in order to avoid leaking memory.

The gorilla/context readme pretty clearly says it's deprecated and conflicts with Golang 1.7+'s inbuild context package.

Which makes things sound like running gorilla/sessions with Golang 1.7+ is a bad idea. Which I'll probably find out shortly, as I'm setting things up now for some basic validation / load testing. 😄

from scs.

This should be ready to go, just waiting on approval of my PR

from scs.

Excellent @royallthefourth, well done. 😄

from scs.