v3 ToU and Consent "whiteboard"

[Cantor, Scott]

On 3/18/14, 11:33 AM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>If we shared a physical office, after lunch I would try to grab one or
>two people with some familiarity with uApprove and ask them to help me
>draw on the whiteboard.

We do have virtual whiteboards if we need it.

>I would leave the center of the whiteboard open, so that after drawing
>the left and right sides I would try to abstract a generic flow in the
>center, which could be re-used in both cases. I guess the abstract
>flow would be something like "stored attribute toggle".

I had been considering how to hopefully just merge the capability into one
flow that would optionally include each piece.

>Given that we have not done any of the above, does it sound reasonable
>to try to implement some sort of generic flow ?

I think if it's not one flow anyway, it may not overlap much because we'd
probably end up with separate context types to prepare to enter each flow,
so I'm not sure what's common in the end if the preamble and the guts
aren't the same.

>Other issues I would bring up regarding v3 Tou and Consent would be :
>in v3 we are not implementing Servlets but rather subflows,

Specifically, if you wanted to do servlets (or even allow it), then the
only state you get is the container session state, and you have to issue a
redirect out of the web flow and then back in. As with the external login
handler use case, but feeling was that it's easier to just build views
than to try and hack in redirects back and forth.

I don't love MVC particularly, but that aside, the view mechanism is
pretty simple to use and I got it working with both JSP and Velocity. The
tricky bit is when to diverge and assume JSP because of some feature or
another that's too hard to build without Java. And of course the downside
to JSP is the horrendous requirement that views have to live inside the
war.

> and I believe we have agreement to try and re-use the StorageService API
>hopefully with a JDBC and LDAP impl.

"Try" probably the key there, since I didn't design for this use case and
I don't know how it fits. To make it work, I think it's likely to mean
serializing to JSON blobs again. I'mfairly certain that will work, but
whether it provides enough visibility into the data for reporting, I don't
know.

-- Scott