I knew you guys wouldn't be implementing it that way, but the demo sort of gives that impression so the clarification is helpful.
And as far as what most people are using, I'm not sure. However I have seen other discussions about implementing such authentication and retry queues via the default transport, so I think this would have a place. But we'll know for sure once one of the heavy hitters like Mr. Broyer weigh in. On Wednesday, July 24, 2013 7:54:02 AM UTC+2, salk31 wrote: > > Thanks, > > We use CAS (single sign on) so what we do is hide the "retry/please wait" > message on auth failure and use an iframe to show the CAS login. If they > login with that form (or somewhere else) then on a retry the app carries on. > > I've very little idea what auth most GWT/RequestFactory people are > using... > > The demo is at least confusing though. I'll try and make it a bit more > realistic. > > Cheers > > Sam > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
