1 Feb
2006
1 Feb
'06
8:56 a.m.
Hello,
you are right. This is a problem with current PA/RLS modules.
The solution using some dynamic xcap root is possible, but still may be
problematic. Better could be explicitly give xcap root as parameter to
handle_subscription or something like this (this is problem too because
of very near future of other parameters for XCAP queries like username,
password, authentication type ...).
Vaclav
On Tue, Jan 31, 2006 at 06:51:45PM +0100, Adrian Georgescu wrote:
Hello Vaclav,
I cannot manage to handle the same username under different domain
names using the same XCAP tree.
Data location for user1(a)example1.com will conflict with data location
for user1(a)example2.com
on the filesystem is the same:
/xcap-root/pres-rules/users/user1/presence-rules.xml
My XCAP server can generate separate trees for each domain and create
the XCAP structure under each domain
(like /xcap-root/example1/pres-rules/users/ ) but in this case SER
should be able to build a dynamic root like:
https://xcap.example.com/$domain$/
In Eyebeam I can configure the xcap-root statically but obviously if
I do this for multiple domains, SER should be able to build it from
information available in the PUBLISH/SUBSCRIBE request so that it can
locate the right tree on the XCAP server.
Do you see any other solution for this problem?
Regards,
Adrian
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers