4

I created a DotNetOpenAuth MVC 2 project using the visual studio template, and have it working. However, the sign in page takes a long time to load. Not quite sure exactly what is going on in the library, but it seems like there is some kind of javascript slowing down the login image button UI from rendering quickly.

I'd like to instead use the openid-selector on the client, rather than the MVC helpers from the DotNetOpenAuth library. What kinds of client & server hooks is the HtmlHelper in this example hiding?

danludwig
  • 46,965
  • 25
  • 159
  • 237
  • 1
    I was able to get it to load more quickly by moving a lot of the DLL resource references (AXD files) into the MVC project and combining them. Getting rid of jquery-ui helped too. Honestly, I think I can do without a lot of the HtmlHelper client-side code. I'd also like to add buttons above and beyond what are in the MVC template. Ultimately, having control over what's going on in the client should make it easier to debug and understand what's going on. – danludwig Aug 30 '10 at 16:06

2 Answers2

2

This post shows how to integrate DotNetOpenAuth and openid-selector: http://blog.tchami.com/post/ASPNET-MVC-2-and-OpenID.aspx

Andriy Gerasika
  • 118
  • 7
1

The openid-selector client, if you're talking about the one like StackOverflow uses, has no server-side hooks at all in the same way that the HtmlHelper's in DNOA use, since the openid-selector makes no AJAX calls back to the server. DNOA's selector control uses AJAX a lot to provide users with an auto-login experience, auto-discovery as they type in the identifier, etc.

So in short, yes, the openid-selector (SO-style) is much simpler and works great with DNOA as well.

And yes, DNOA's built-in AJAX selector loads more slowly. That's something that I (or a volunteer) still need to work on speeding up.

Andrew Arnott
  • 80,040
  • 26
  • 132
  • 171