<html><head/><body><html><head><meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /><meta content="text/html; charset=UTF-8" http-equiv="Content-Type" /></head><body bgcolor="#FFFFFF" text="#000000">Hi,<br>
<br>
could you please shed some light on the use case for the User field? What entity sets the value, what entitity uses it for what purpose? <br>
<br>
Regards,<br>
Torsten.<br><br><div class="gmail_quote"><br>
<br>
Kingsley Idehen <kidehen@openlinksw.com> schrieb:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="moz-cite-prefix">On 7/18/13 1:38 PM, Torsten Lodderstedt
wrote:<br />
</div>
<blockquote cite="mid:79cf3a27-c0d1-43e1-b1e6-6442e1d2c13c@email.android.com" type="cite">
I fully agree with George und would like to add: why don't you
just use the authorization header to send identity
data/credentials/tokens to the server in order to allow for access
control?<br />
</blockquote>
<br />
This is already possible. The requirement here stems from the fact
that "From:" is bound specifically to mailto: scheme URIs (Uniform
Resource Identifiers). We are looking to "User:" to be the
superClass of "From:" which is basically URI scheme agnostic. That's
it. <br />
<br />
[SNIP]<br />
<pre class="moz-signature" cols="72">--
Regards,
Kingsley Idehen
Founder & CEO
OpenLink Software
Company Web: <a class="moz-txt-link-freetext" href="http://www.openlinksw.com">http://www.openlinksw.com</a>
Personal Weblog: <a class="moz-txt-link-freetext" href="http://www.openlinksw.com/blog/~kidehen">http://www.openlinksw.com/blog/~kidehen</a>
Twitter/Identi.ca handle: @kidehen
Google+ Profile: <a class="moz-txt-link-freetext" href="https://plus.google.com/112399767740508618350/about">https://plus.google.com/112399767740508618350/about</a>
LinkedIn Profile: <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/kidehen">http://www.linkedin.com/in/kidehen</a>
</pre>
</blockquote></div></body></html></body></html>