I'm in the process of putting together a pull request to add a Memcached Proxy Ticket Manager to the ASP.NET CAS Client, similar to the Java Memcached PGT Storage option. The issue I'm having is that a new Reference, to the Enyim Memcached library, is required to add this feature. It doesn't seem too elegant to include a new Reference DLL with the ASP.NET CAS Client distribution because of one feature that not a lot of users will need. Any thoughts on how a Reference should be added for an occasional feature like this? It looks like there are three possible options. Late binding which results in ugly code, use a different build configuration for Memcached, which is not very maintainable, or a dependency injection framework, such as StructureMap. Any thoughts on what direction to go?
-- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
