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-nam
Peter Dunkley writes:
> 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
Hello,
FWIW, the following XCAP AUIDs are not yet supported by the xcap-server
module:
- geolocation-policy
- org.openmobilealliance.accessrules
- org.openmobilealliance.conv-history
- org.openmobilealliance.deferred-list
- org.openmobilealliance.groups
- org.openmobilealliance.group-usage-list
-
Hi,
org.openmobilealliance.xcap-directory isn't supported by the xcap-server module.
Adding support for this shouldn't be difficult though.
Regards,
Peter
Juha Heinanen wrote:
>in xcap module readme there is an example xcap server config file and it
>does not include in xcap-caps aiud
>org
in xcap module readme there is an example xcap server config file and it
does not include in xcap-caps aiud
org.openmobilealliance.xcap-directory. does it mean that xcap-directory
application is not currently supported or could the aiud just be added
there?
-- juha
_
