+1<br><br><div class="gmail_quote">On Wed, Feb 17, 2010 at 7:44 AM, John Bradley <span dir="ltr"><<a href="mailto:ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I agree that there is no practical use for the association handle if we have a per artifact secret.<br>
<br>
That is why it may be useful to think of artefact as something not dependent on the existing redirect binding.<br>
<br>
John B.<br>
<div><div></div><div class="h5">On 2010-02-16, at 6:34 PM, Allen Tom wrote:<br>
<br>
> Hi John -<br>
><br>
> I was not suggesting that everyone use Artifact binding - presumably the OP<br>
> will indicate that it supports Artifact binding in its discovery document,<br>
> and it'll be up to the RP initiate the artifact request.<br>
><br>
> Also, regarding my previous proposal to ditch the association request for<br>
> artifact binding - I concede that artifact binding is orthogonal to<br>
> associations.<br>
><br>
> However, if one of the goals of artifact binding is to shorten the size of<br>
> the requests/responses, then eliminating the association handle would be<br>
> consistent with this goal.<br>
><br>
> Allen<br>
><br>
> On 2/16/10 1:09 PM, "John Bradley" <<a href="mailto:ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a>> wrote:<br>
><br>
>> We can't force everyone to do artifact. We will still need to support<br>
>> associations in RP's.<br>
>> We cant just ditch the concept completely.<br>
>><br>
><br>
<br>
_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a><br>