Starting from text, means that you can keep this documentation easily in git, and you can use maven or many other processes to generate the docs automatically (much like you do with Markdown).
Sounds like it has all the properties we want for high-quality, maintainable documentation. I didn't read the source of your proxy sequence too carefully but at first glance it looked pretty readable even in plaintext form.
I wondering if the developers feel that these diagrams would be useful to include with the documentation.
I think they would be an excellent addition to the protocol documentation section.
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