<div dir="ltr">Thanks,Maybe simplify this question is more reasonable,I will try this first.<div><br></div><div style>BR,</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/6/3 Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On Jun 3, 2013, at 1:58 PM, Yuming Zheng wrote:<br>
<br>
> What means the user-input element?<br>
<br>
</div>This one: <a href="http://tools.ietf.org/html/rfc4480#section-3.14" target="_blank">http://tools.ietf.org/html/rfc4480#section-3.14</a><br>
<div class="im"><br>
> Actually device can compare the tuple id from the rpid with himself to keep different presence state himself if he<br>
> subscribe the presence to himself.<br>
<br>
</div>Correct. You can use the instance ID as the tuple ID, for example. Hence the contact element would contain the GRUU to reach that particular user.<br>
<div class="im"><br>
> and in another case, the two devices can make the state synchronized with each other if he<br>
> subscribe the presence to himself and do not care the tuple id.<br>
> So,practically,what is reasonable choice to implement by the client?<br>
><br>
<br>
</div>In Blink we started by having different presence states per device, XMPP style, but in practice this brought some trouble so we went back and implemented it in a way all presence states are synced for a given AoR, essentially what Skype does.<br>
<br>
<br>
Regards,<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>