strong +1 … as long as XML stays the default if param is missing on current validation uri’s.
Additionally, I recommend to support content negotiation by Accept header and uri extension (.json / .xml) from clients, e.g. by using Spring ContentNegotiationManager. Robert > Am 08.09.2015 um 16:54 schrieb Misagh Moayyed <mmoay...@unicon.net>: > > Team, > > Jérôme and I have been discussing the possibility of extending the CAS > protocol to add an optional parameter/feature applicable to service > validation. The idea is to allow CAS to produce the validation result in > alternative formats other than XML, with the first candidate being JSON. We > would keep the default behavior with XML as things are now, and the new > parameter may be recognized by implementations that actually support that > option. > > What do you think? > > Misagh > -- > You are currently subscribed to cas-dev@lists.jasig.org > <mailto:cas-dev@lists.jasig.org> as: robertoschw...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- 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
