10 Oct
2012
10 Oct
'12
2:35 p.m.
On 10/10/12 11:55 AM, Olle E. Johansson wrote:
10 okt 2012 kl. 11:09 skrev Daniel-Constantin Mierla
<miconda(a)gmail.com>om>:
They are in the XML, so we might not have to store them. You need them for verifying the
document as valid.
But we do need the XML doc format.
Btw, the XCAP client and XCAP server seems to have different views of table version # in
3.3.1.
That was fixed in master long time ago, but I think the backport was
done long after that, now it is same version in 3.3 branch. So upcoming
3.3.2 will have it right if older 3.3.x don't have it.
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
On 10/10/12 9:10 AM, Olle E. Johansson wrote:
Yes. Every AUID defines an
XCAP URI part, a URN for XML verification and an XML document format.
Is there a reason why we don't save the XML
media tag (Content-type) for XCAP documents?
the xcap_server module was developed
to reuse existing xcap table. Are there different content-types for the documents
published via xcap? If yes, then we have to store it.
Aren't we supposed to reuse the media tags in a GET operation?
I see that I can add AUIDs, but not URNs or Media tags for these application usages.
What is the purpose of storing URNs? How many can be stored for an xcap doc.