Team, In line with the CAS4 coming release and CAS-1145 [1], [which in brief proposes to separate out protocol specific details from the implementation and in particular, parameters to URL endpoints], I wanted to ask for the team's suggestions on how best this may be achieved. Currently, it's somewhat difficult to differentiate for instance, between a "service" parameter that is part of the protocol and one that is simply used for internal implementation. This changeset should also align well with the upcoming updates on the protocol doc itself.
I had originally thought that protocol specific details could perhaps become part of the CAS API itself. Scott mentioned that the CAS4 branch had already carried out this separation to some serious extent. What might be the best way to take appropriate changes from that branch and merge into master? Regards, -Misagh [1] https://issues.jasig.org/browse/CAS-1145 -- 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
