> I'm very interested in collaboration. My goal is to create a > community supported open source JASIG .Net CAS client that has feature > and quality parity with JASIG Java Client and excellent integration > into ASP.NET framework.
We're on the same page, then. We are _particularly_ interested in the HttpModule-based design you mentioned. That would provide a route to direct support for CAS in IIS through the capability of IIS 7 to use ISAPI modules written for the .NET runtime. Direct IIS support is sorely lacking at the moment, and this would be a significant benefit as the install base for IIS 7 grows. We are also interested in creating a multi-protocol client. That is one area where the design of the Java CAS client shines. > I trust Scott's design instincts, so my current approach is a pretty straight > forward port of the class hierarchy. I agree that the design of the Java CAS client is solid, and worth modeling. We did a cursory review the CAS client Paul mentioned, and we felt a start-from-scratch port of the Java client was a better way to go. > I've got about 15 hours into the port and a > handful of interfaces and classes.... > I'm happy to check in what I've got to the JASIG SVN. I would recommend we set up some SVN space in the Jasig repository, and get to work. Scott, can you help with that? M (is for Marvin ;) -- 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
