Hello,
On 9/7/11 11:24 AM, laura testi wrote:
Hi Daniel,
thank you for your quick reply. We have already tried with node
selector '~~' after doc uri in the http XCAP PUT request. But We got
the error "ERROR: xcap_server [xcap_misc.c:60]: http uri too long"
then "ERROR: xcap_server [xcap_misc.c:736]: error setting xcap uri data...".
I think that it can be a limitation of the MAX URI length which
actually it's set to 128. Maybe also something else.
the error is because the
size of http url is higher than 127. You can
increase it, no problem, it is now 255 in devel version -- be aware you
have to increase in the database xcap table as well the size of doc_uri.
Cheers,
Daniel
We'll try to increase the max length definition and see what happen.
Any other suggestion?
Thank you much again.
Best Regards,
Laura
On Wed, Sep 7, 2011 at 10:37 AM, Daniel-Constantin Mierla
<miconda(a)gmail.com> wrote:
> Hello,
>
> On 9/6/11 3:25 PM, laura testi wrote:
>> Hi,
>> I am using the XCAP server of kamailio for contact list and presence
>> rules. It seems it only support to update the whole xcap doc of the
>> user but not the partial update. Can anyone tell me if the kamailio's
>> xcap server support the partial update of a user's doc? for example,
>> to remove a contact from the contact list or add a contact to the
>> contact list without PUT or DELETE the whole xcap document of this
>> user? If yes, what's the syntax of the HTTP request?
>>
> it should work using the node selector '~~' and then XPath format to point
> the part to be updated. This is actually in the HTTP URL, rfc4825 has some
> examples, iirc.
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla --
http://www.asipto.com
> Kamailio Advanced Training, Oct 10-13, Berlin:
http://asipto.com/u/kat
>
http://linkedin.com/in/miconda --
http://twitter.com/miconda
>
>
--
Daniel-Constantin Mierla --
http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin:
http://asipto.com/u/kat
http://linkedin.com/in/miconda --
http://twitter.com/miconda