On Oct 1, 2010, at 2:12 AM, Iñaki Baz Castillo wrote: > 2010/9/29 Adrian Georgescu <a...@ag-projects.com>: >> Hello, >> >> There is a new release of OpenXCAP, version 2.0.0 It contains many bug >> fixes and buddy lists management based on OMA XDM specifications related to >> SIP SIMPLE presence. > > Hi, let me some comments inline: > > * Added OMA XDM support for Buddy Lists Management > > AFAIK OMA specs for buddylist management is not adopted. Instead IMS > uses RCS specs which includes some changes to OMA specs, specially in > buddylist management. Perhaps I am wrong and there are clients > implementing OMA specs for buddylist?
Yes, keep the faith. >> * Check external references for pres-rules and resource-lists > > How such check is done? We simply won't allow external references, all resource must be local and belong to the same user. >> * Don't allow external-ref paths which don't point to an 'entry' > > What about if that 'entry' is deleted later after the external-ref > path is created? I am not sure what this means. You may check the commit for that change to get the insight of what it does. >> * Check entry-ref entries in resource-lists > > OMA prohibits the usage of entry-ref. Just external-ref is allowed. > entry-ref just exists in IETF's incomplete specs. What does OpenXCAP > implement exactly? We support both OMA and non-OMA requests. > Regards. > > > > -- > Iñaki Baz Castillo > <i...@aliax.net> > > _______________________________________________ > Devel mailing list > Devel@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel