[OpenSIPS-Users] Learning about resource lists

[Adrian Georgescu]

Hi Bogdan,

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.

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.

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.

—
Adrian




> On 22 Nov 2023, at 07:02, Bogdan-Andrei Iancu <bogdan at opensips.org> wrote:
> 
> HI Adrian,
> 
> 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 ?
> 
> Thanks and regards,
>  Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com <https://www.opensips-solutions.com/>
>   https://www.siphub.com <https://www.siphub.com/>
> On 11/20/23 11:11 PM, Adrian Georgescu wrote:
>> XCAP is a failure. Not that we did not try, it was a bad idea and it failed.
>>  
>> —
>> Adrian
>> 
>> 
>> 
>> 
>>> On 20 Nov 2023, at 14:27, Robert Dyck <rob.dyck at telus.net> <mailto:rob.dyck at telus.net> wrote:
>>> 
>>> 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.
>>> 
>>> <resource-list>https://xcap.example.com/xcap-root/resource-lists/users/sip:alice@example.com/index/~~/resource-lists/list%5b@name=%22l1%22%5d</resource-list>
>>> 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?
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> 
>> 
>> 
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231122/7316b672/attachment.html>