Nice. Do you know if this will work with or against web.py/GSoC's session module? Should/could they be [easily] integrated?
Upon first glance I have a quick question about the following line: 143: osession.userid=strip_url(info.identity_url) Here's a use case describing the problem I identify myself as: http://students.ucsb.edu/john_doe/ The module strips the prefix and trailing slash and consuming web.py app stores the following as the ID: students.ucsb.edu/john_doe What if the page representing my identity can only be found at the following: https://students.ucsb.edu/john_doe/index.htm Although rarely used I believe the matter of normalization is a critical issue specifically in cross-site aggregation of identity features. It's difficult to make assumptions about URIs and XRIs should technically be supported as well (ugh) so check this out and let me know what you think: Normalization @ OpenID 2.0 Spec<http://openid.net/specs/openid-authentication-2_0-12.html#normalization_example> . On 9/26/07, Aaron Swartz <[EMAIL PROTECTED]> wrote: > > > > Fantastic! This is like the best news I've heard in years. > > It's up to Anand but I expect he'll do it since he already said he > wanted OpenID in 0.3. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
