On Tue, Oct 14, 2014 at 8:18 AM, George Christman <gchrist...@cardaddy.com> wrote:
> Geoff, I always try to follow you suggested pattern, but unfortunately I > don't think it's always possible. I'd like to present a use case scenario > and perhaps maybe you guys can break me out of my current design rut. > *Use case 1* > *Use case 2* > I guess I'm just not sure how you can accomplish both use cases without > running into an area where a component would not need to command it's > container. > I'm very interested in hearing your thoughts. I'm not opposed to changing > my design to make everything work properly. > My original response still stands and I know what you are trying to accomplish but it gets tricky trying to get it all done asynchronously, and in general I advice to just handle sign-in/sign-up via a full page refresh. There are multiple reasons for it: - you are likely going to support full login page anyway, so the clever XHR flow is not required - the screen real estate get crowded once you add sign-up to the same flow - if you add Oauth, it's best practice to do full page refreshes - available security frameworks have better support for full page refreshes - design for mobile - modal dialogs often have fixed sizes, makes sure all your users see the necessary stuff without scrolling (especially sideways) - if you allow plain http for your site, async flow won't work when you switch to https for authenticated users Just as an anecdotal evidence and totally IMHO, stackoverflow.com has one of the best designs out there for sign-in/sign-up flows and they are doing it as a separate page as well. Kalle
