Hi, Configuration directions are much easier to adapt to specific implementations. Having basic authorization support may also help to get sites up quickly.
Thanks, Russ On Mon, 13 Nov 2006, Stephen A. Cochran wrote: > > On Nov 8, 2006, at 9:54 AM, Scott Battaglia wrote: > >> If you guys are interested in developing this, we welcome its >> development under the auspices of JA-SIG, which would grant it >> access to all JA-SIG tools (LuntBuild, CVS, JIRA, etc.). You guys >> would be in charge of the specific project, release schedules, >> etc. If you're interested in this, let's move this discussion to >> the cas-dev list! > > Instead of putting the time into my mod_cas update, I'm wiling to > consolidate the changes from the three (at least) updated versions. > My plan would be to integrate the APR XML parsing Ken did in place of > my manual parsing. I'd also keep the APR shared memory cache that > several of the modules used. > > One question is if end users would want some basic authorization > support to stay in, or if it should be stripped out entirely. > Thoughts? I personally feel that having basic authorization and the > "all in one stop" module might be nice for a lot of sites. Could be > enabled/disabled via compile or config directives. > > Once I build up some consensus I'll post back the design overview and > get the projects merged. If anyone an URL for the VA Tech and Ken if > you could send me a link to your APR-XML enhanced version, that would > be helpful. > > Steve Cochran > Dartmouth College > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
