23 Sep
2012
23 Sep
'12
7:43 p.m.
xcap-directory is a sensible feature to add to the xcap-server module.
One of the problems with XCAP is that a client can give the documents any
file-names they want (so you could have a resource list called
contacts.xml or resource-list.xml). Each client seems to use a different
default file-name which means you can't easily switch between clients.
With xcap-directory a client will be able to easily see if an XML document
of a particular type already exists (regardless of what its default
file-name is). So it should help with interworking.
Of course, being an Open Mobile Alliance (rather than IETF) AUID means
that the few clients that do support XCAP probably don't support
xcap-directory. On the other hand, the more XCAP servers that support
this, the more likely it is that clients will - which should improve
interoperability of SIP presence in general.
Regards,
Peter
Peter Dunkley writes:
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
Most of these are trivial to add - supporting a
new AUID that is just a
static document is around 10 lines of code (although the existing
presence
modules don't support those features so just adding to the xcap-server
may
be of limited value). However, (at least) two are more complex. As I
mentioned, the xcap-directory AUID should be fairly simple to add (a day
or so of work I think). However, supporting search requires
implementation (or integration) of an XQuery engine which makes this a
very big task.
Peter,
Thanks for the explanation. I asked because of this requirements list:
http://projects.ag-projects.com/news/15
OpenXCAP server has support for xcap-directory, but i don't know what
kind of searcher can be made from it.
-- Juha
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users