Shibboleth Developers

["Scott Cantor" <>]

> There are memcache binaries for most OSes/distributions. Memcache works
> with the default options... You just have to start the daemon, no
> configuration files... :)

Foolproof, huh? Famous last words...;-)

> Personally I don't like any kind of stickyness... And some
> load-balancers don't support it in any form, let alone sticky sessions
> with timeout..

I'm just saying my approach has worked for every application here except for 
one, and they just used the "one shibd" approach as a stop gap. Some testing 
would be required, but I have a suspicion that with 2.0, the performance 
difference is probably pretty minimal between using memcached and running one 
shibd and sharing it. Just a thought.

> Yes, it's not persistent. What will happen if a memcache server fails
> (and I haven't seen this happen) is that sessions stored in that server
> will disappear and people will have to login again, no biggie.

You also lose the replay cache (and artifacts, but nobody uses those). As far 
as it being a big deal, that's really a matter of opinion. My point is that 
people should understand the difference between a persistent cache and an 
in-memory cache. This one's in the middle.

> Attached is a patch which includes the plugin and modifications to
> configure.ac and a new Makefile.am.

It will definitely be in 2.1, but I don't have an ETA on that. 2.0.1 should 
be out pretty soon.

-- Scott