2010/5/28 Daniel-Constantin Mierla <[email protected]>: > > Hi, in XCAP there are 4 HTTP methods: GET, PUT, DELETE and POST (POST > > is just used in OMA search application). > > How are these HTTP method supposed to be mapped into SIP? > > > The draft I mentioned below has specs for store/remove documents, so I > thought can be re-used (extended), something like: > > Content-Disposition: script;action=PUT
Hi, XCAP bodies *always* contain XML documents (no scripts, no images), so I don't see the benefict of using such complex "Content-Disposition" header with the XCAP method set in a header parameter. NOTE: OMA specifies "org.openmobilealliance.pres-content" XCAP application which is mainly used to carry avatar/icons, but such images are also embedded into a XML node, encoded in Base64. > > IMHO an easier approach would be defining a new SIP method (i.e. > > "XCAP") and adding two headers for XCAP action and uri). > It is an option, we support that already :-) in these SIP servers -- you > know. I don't want to miss any draft/rfc that has specs for such cases. Well, you already know what I think about the whole XCAP/SIMPLE (for presence) specifications. IMHO the main problem is not the transport layer of XCAP but its complex and inneficiente application level. Let's speak about this soon ;) -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
