Walden Sorry for your head ;). On Tue, Nov 18, 2008 at 7:29 PM, walden <[EMAIL PROTECTED]> wrote: > > Olivier, > >> * session expiration, because the GWT RPC will fail soon (401). >> * forbiden because the GWT RPC will fail soon (403). When session is expired, the RPC will fail soon with a 401 (Auth required status), before GWT 1.5 it was not (easily ) possible to detect such failure. But session expiration is not an issue for HTTP basic. >> * activation of widget when authority is granted. > > I'm scratching my head wondering what those mean. In my app, RPC's > are secure and they don't fail. As for widget activation, you're > talking authorization, and I don't see any difference among the > proposals on that. > About widget activation && authorization, I my proposal the widget are aware of the authentication events so they can activate/desactivate when login/logout occurs.
> >> * logout (not possible with HTTP Basic). > > And yet I have it. Go figure. > > > Walden > > > > -- Si l'ignorance peut servir de consolation, elle n'en est pas moins illusoire. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
