"thesamet" <[EMAIL PROTECTED]> writes: > Have you looked at the patch I submitted at > http://trac.turbogears.org/turbogears/ticket/930 ?
I haven't looked at it. I'm commenting your message. > The main difference is that the identity lives inside a BrowserSession > object (as a cookie) and is not global. Therefore you can have several > "browsers" interacting with the application. It's very useful when you > want to test if user A is affected from user B's actions. BTW, > BrowserSession tracks all cookies, and not just the visit cookie, so > it's useful for many other tests. > > The con in BrowserSession is that you actually have to browse to /login > in order to link the session with an identity. But this can be remedied > by adding something similar to attach_identity to the BrowserSession. > > What do you think? How about using multiple tabs? Do each instance of the browser reuses the authentication? What happens on IE when you open a new window? Is the BrowserSession shared among these windows? I liked your idea. It is very interesting. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
