So where did we land in terms of design proposals? The following jumped out me as worth pursuing:
1. Factor out ticket storage concerns into a high-level storage service component 2. Factor out authentication concerns into a high-level authentication service component The first will allow us to have a single integration component for storage-specific backends instead of multiple as we do now; for example, a single DatabaseStorageService that could be used for both tickets and services instead of JpaTicketRegistry and JpaServiceRegistryDaoImpl. That seems beneficial from a support perspective as much as design; one fewer component to keep up with as the technology-specific integration libraries (Hibernate, spymemcached, Infinispan) change. As for authentication service, how would it differ from the existing AuthenticationManager component? I like the idea, but I'm not clear on its responsibilities. We might also consider consolidating the session start/stop mechanics into a service component (SessionManager). That's one of the main concerns of CentralAuthenticationServiceImpl at the moment, and factoring that out might point the direction for how to handle the remaining concerns. M -- 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
