<HTML>
<HEAD>
<TITLE>Re: [OpenID] Automating the user's selection of OP</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Thanks for your feedback.<BR>
<BR>
> 1) Detecting logged in status for a set of OP's even if it is possible, will<BR>
> mean an extra delay in the login process.<BR>
<BR>
The detection can be done in the background, in parallel, and the results displayed only once they come back. If the OPs are fast, then loading from 20 OPs generates 40 HTTP requests (20 if you optimize the return_to). This is no worse than loading 40 images on a page.<BR>
<BR>
> 2) Even if you detect a person logged in to an OP we cannot assume that it<BR>
> is the OP the user would like to use for the particular RP.<BR>
<BR>
That’s true. The user still needs to choose to login, but at least now the RP can place the choice much more prominently than it would be able to without this information.<BR>
<BR>
‘> 3) You may find the user logged in to more than one OP's,<BR>
<BR>
I specifically addressed that objection in my post. If the user is logged into more than one OP, then you can still give them a choice.<BR>
<BR>
> You might as well ask the question at the start itself and set a cookie for the user.<BR>
<BR>
With this technique, you could run the detection for a much larger set of OPs, and ask a more intelligent question. Otherwise, how do you ask a user to choose from 100 services, most of which they have never heard of?<BR>
<BR>
In any case, this suggestion has yet to be implemented. The right way to tell if this is correct is to implement and test to see if it performs better than the NASCAR approach.<BR>
<BR>
On 4/20/09 6:47 PM, "Santosh Rajan" <<a href="santrajan@gmail.com">santrajan@gmail.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Chris Messina wrote:<BR>
><BR>
> Luke Shepard wrote about this idea recently:<BR>
><BR>
> <a href="http://www.sociallipstick.com/2009/04/15/lets-detect-logged-in-state/">http://www.sociallipstick.com/2009/04/15/lets-detect-logged-in-state/</a><BR>
><BR>
<BR>
Does not look like a practical idea to me.<BR>
<BR>
1) Detecting logged in status for a set of OP's even if it is possible, will<BR>
mean an extra delay in the login process.<BR>
2) Even if you detect a person logged in to an OP we cannot assume that it<BR>
is the OP the user would like to use for the particular RP.<BR>
3) You may find the user logged in to more than one OP's,<BR>
<BR>
So you are still back to asking the user which OP's he would like to login<BR>
with.<BR>
<BR>
You might as well ask the question at the start itself and set a cookie for<BR>
the user.<BR>
<BR>
<BR>
-----<BR>
<BR>
Santosh Rajan<BR>
<a href="http://santrajan.blogspot.com">http://santrajan.blogspot.com</a> <a href="http://santrajan.blogspot.com">http://santrajan.blogspot.com</a><BR>
--<BR>
View this message in context: <a href="http://www.nabble.com/Automating-the-user%27s-selection-of-OP-tp23134539p23147925.html">http://www.nabble.com/Automating-the-user%27s-selection-of-OP-tp23134539p23147925.html</a><BR>
Sent from the OpenID - General mailing list archive at Nabble.com.<BR>
<BR>
_______________________________________________<BR>
general mailing list<BR>
<a href="general@openid.net">general@openid.net</a><BR>
<a href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>