> +1 for reverting /serviceValidate to CAS2 protocol/CAS3.x release > behavior (deployers can continue to overide as required). This > ensures backward compatibility for all current CAS clients. > > +1 for new /p3/serviceValidate for CAS3 protocol multi-value attribute > release. This provides optional enhanced features for clients that > support it.
I'm strongly in agreement with Bill on this. +1 on each of the above for me. > Regarding JSON and other protocol enhancements, perhaps that should > wait until 4.0GA is out the door. Agreed. I think a JSON format is a great idea, but I don't necessarily agree that adding endpoints is the way to go. Any new feature or capability at this point simply clouds the important issue at hand regarding backward compatibility. The proposal above offers a simple solution that ensures safety. Let's take it and move forward. 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
