On Thu, Mar 4, 2010 at 5:26 PM, Scott M. Holodak <sholo...@princeton.edu> wrote: > Hi, > > I’ve made a number of commits to the dotnet-casclient project over the past > few weeks and I would like to get some feedback on the code > (CasAuthenticationModule.cs, CasAuthentication.cs, and the ExampleWebSite > which is based entirely on the CasAuthenticationModule) to help determine > the best path forward. [snip] > The changes light up many > of the features in the .NET framework that are unavailable with the > CasAlternateAuthModule or the previous version of the > CasAuthenticationModule (URL Authorization, Membership provider support, > Role-based security, User/role varied page caching, Code Access Security, > etc.).
Very cool and consistent with the draft Roadmap goals: http://www.ja-sig.org/wiki/display/CASC/.NET+CAS+Client+Vision+and+Roadmap [snip] > > I have three possible paths in mind: > > - Branch development and separate the modules. Since I haven’t > yet committed any changes that break the alternate module, I would advise > that the Alternate module be treated as the last revision before my first > commit. > > - Remove the alternate module from the trunk and focus > development efforts on the Forms-based CasAuthenticationModule > > - Have the CasAlternateAuthModule maintainers update their code > to make use of the CasAuthentication static API implementation and actively > sync with API changes. > Initially, there were two thoughts about how best to implement the required CAS behavior via HttpModules, and agreement to build them both based on a common core CAS Domain Model. However, given the direction and leadership you've shown with CasAuthentication, I think it's reasonable to consider focusing on the one approach. My thoughts would be to drop the AlternateAuthModule unless someone can come provide a compelling reason to keep it around and wants to commit to keeping it up to date with the API changes. Bill -- 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
