If you guys have any learnings from that, i.e. missing opportunities for better extension points, etc. that would be valuable feedback!
On Mon, Jul 30, 2012 at 12:44 PM, Dmitriy Kopylenko < dmitriy.kopyle...@gmail.com> wrote: > > I'm fairly certain we can by leveraging what has been arguably the >> best tool for extensibility in the CAS project: Spring Webflow. With >> a fairly simple set of components that are conceptually similar to the >> existing ArgumentExtractors, we could dispatch each protocol to a flow >> that is designed to support it specifically. In my mind the beauty of >> this approach is that we don't have to add new URIs for each protocol >> we support and we don't have to architect a single API for all >> existing and future protocols, which seems like the biggest barrier to >> designing more robust multi-protocol support. Webflow has allowed us >> to add a number of new and interesting features to CAS in an >> extensible and backward compatible fashion; I'm fairly certain we >> could do the same with protocol support. >> >> > And one example of this flexible extensibility would be adding custom WIND > protocol to CAS that we did for Columbia University, without the need for a > custom CAS codebase fork nor messing around with internals of CAS' core > components e.g. CentralAuthenticationServiceImpl, etc. > > Dmitriy. > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- 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
