I took a pass at JIRA and updated issues that are fit for CAS 4. There are 3 that are ready to merge with pulls pending and then remains support for multi-valued attributes and creation of new endpoints: http://bit.ly/18Ac6HV
CAS-1283 is supposed to ensure that multi-valued attributes are properly encoded in the response unflattened, and then there is CAS-1381 under which I am assuming that we want to carry out creation of new endpoints, etc that are discussed on this thread. Is this an accurate summary, so that we can begin tackling #1283 and #1381? Misagh ----- Original Message ----- From: "Marvin Addison" <[email protected]> To: [email protected] Sent: Monday, December 2, 2013 2:21:53 PM Subject: Re: [cas-dev] CAS Protocol v3 Status > +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 [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
