If I may suggest, I think the logical next steps would be: 1) Have a sketch (and iterate over) concrete APIs for these subsystems 2) Create a small but functional prototype implementation wiring all the core components together (just a login screen with mock implementations e.g. in-memory, etc.). Perhaps use a fresh “POC” repo for that. And iterate based on the outcome, etc. Validate ideas and design early and often, etc.
Again, that would require some time investment from interested folks, but if there is a real interest, that should be possible. Does this sound too “crazy”? Cheers, D. > On Dec 9, 2014, at 9:45 AM, Marvin Addison <marvin.addi...@gmail.com> wrote: > > I guess we need to update and review a little more this draft > (https://wiki.jasig.org/display/CAS/CAS+5+Design > <https://wiki.jasig.org/display/CAS/CAS+5+Design>), just to improve our ideas > and thinking. Then, we can set up a call. > > +1 > > So far, it references 3 components: > - the AuthenticationService ... > - the Storage service ... > - the session manager ... > > I drafted a diagram last year with those three components showing how they > integrate with the HTTP layer above and storage layer below that I hope will > be useful: > > https://drive.google.com/file/d/0Bw8LSvcVZrEvdVdibnVKQ2E0aWs/view?usp=sharing > <https://drive.google.com/file/d/0Bw8LSvcVZrEvdVdibnVKQ2E0aWs/view?usp=sharing> > > Feel free to attach that diagram to the Wiki page if you find it helpful. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org > <mailto:cas-dev@lists.jasig.org> as: dkopyle...@unicon.net > 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
