<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Bogdan,<div><br></div><div>My two cents. The reality is that adoption of XCAP is practically zero. Even if you build a client, you cannot make it interoperable with another, and XCAP was suppose to be interoperable. If I build a buddy list on one client and I cannot load it in another client, it makes no sense.</div><div><div><br></div><div>I think that anyone building a SIP app that needs to store/fetch data on the SIP server can better do it using PUT/GET with a JSON, for example we took this path for Sylk client rather than implementing XCAP again. This is not interoperable between different clients, but there is no replacement standard for XCAP either and is much cheaper and more reliable to do it like this.</div><div><br></div><div>As far as OpenSIPS is concerned one can probably make a new module or better, modify that existing RLS module so that it can read contacts directly from a database table with a schema that can be defined by the user. In the end what one needs is a list of URIs and a flag to see who is granted to see your presence, is a very simple database model.</div><div><br></div><div><div><div><div>
<meta charset="UTF-8"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>—</div><div>Adrian</div><div><br></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<div><br><blockquote type="cite"><div>On 22 Nov 2023, at 07:02, Bogdan-Andrei Iancu <bogdan@opensips.org> wrote:</div><br class="Apple-interchange-newline"><div>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div>
<font face="monospace">HI Adrian,<br>
<br>
should we understand the everything related to xcap, like RLS,
buddy list, auth, etc are dropped dead at this time? if so, are
you aware of any replacement / alternatives here ?<br>
<br>
Thanks and regards,<br>
</font>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com/">https://www.opensips-solutions.com</a>
<a class="moz-txt-link-freetext" href="https://www.siphub.com/">https://www.siphub.com</a></pre>
<div class="moz-cite-prefix">On 11/20/23 11:11 PM, Adrian Georgescu
wrote:<br>
</div>
<blockquote type="cite" cite="mid:799FAE93-340B-497D-81B9-2F5E54EC5B54@ag-projects.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
XCAP is a failure. Not that we did not try, it was a bad idea and
it failed.
<div> <br>
<div>
<meta charset="UTF-8">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>—</div>
<div>Adrian</div>
<div><br>
</div>
</div>
<br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<div><br>
<blockquote type="cite">
<div>On 20 Nov 2023, at 14:27, Robert Dyck
<a class="moz-txt-link-rfc2396E" href="mailto:rob.dyck@telus.net"><rob.dyck@telus.net></a> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div>
<div style="margin: 0px;">The context here is
subscription to presence by way of a resource list.
The learning curve is steep. I have read the tutorial.
The tutorial gives an example of a rls-service xml
document. In the example the resource list is
contained within the services document. Various other
examples I have found use a separate document to hold
the list. The services document then references the
list document.</div>
<br>
<div style="margin: 0px;"><span style=""><span style="background-color:#ffffff;"><span style="font-family:monospace;"><resource-list><strong><a class="moz-txt-link-freetext" href="https://xcap.example.com/xcap-root/resource-lists/users">https://xcap.example.com/xcap-root/resource-lists/users</a></strong>/<a class="moz-txt-link-freetext" href="sip:alice@example.com/index/~~/resource-lists/list%5b@name=%22l1%22%5d">sip:alice@example.com/index/~~/resource-lists/list%5b@name=%22l1%22%5d</a></resource-list></span></span></span><br>
</div>
<div style="margin: 0px;">If I use an integrated server
the xml documents reside in a local database rather
than the file system. Http isn't going to work. How
would one reference the database and table using
rls-services document? Or is a separate resource-lists
document not supported when using an integrated rls
server?</div>
</div>
_______________________________________________<br>
Users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>Users mailing list<br>Users@lists.opensips.org<br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br></div></blockquote></div><br></div></div></div></div></body></html>