Right, thanks for clarification. I have set aside some time to review #1381 and at least test CASC and NETC. Will provide results and pulls as I march forward with tests hopefully by week's end.
Misagh ----- Original Message ----- From: "Marvin Addison" <[email protected]> To: [email protected] Sent: Tuesday, December 3, 2013 7:55:25 AM Subject: Re: [cas-dev] CAS Protocol v3 Status > 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. CAS-1283 as written implies CAS protocol v3, so the creation of new endpoints as a solution to provide strict compliance with v3 protocol seems consistent with the scope of that issue. I'm not sure what, if anything, we should do about customizations folks have made to shim attributes into v2 protocol. I would argue that it has been and continues to be a customization folks will need to support on their own. I think CAS-1381 is a high-level issue that we're using to track results of integration testing generally, which includes attribute support in particular. 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
