On Sep 10, 2010, at 9:56 PM, Iñaki Baz Castillo wrote: >> On Sep 10, 2010, at 8:05 PM, Iñaki Baz Castillo wrote: >> >>> 2) The XCAP/XDMS server notifies the user with incremental changes >>> occured in the resource-lists by other UA (wooooow, an HTTP server >>> handling SIP subscriptions!!). >> >> The server must only Publish to the Presence Agent, is the client that >> Subscribes and receives Notifies. > > Perhaps in your implementation, but OMA specs clearly state that an UA > subscribes to the XCAP/XDMS server for changes in its documents.
I assume that one always subscribes to its own URI for presence.winfo and xcap-diff events, and ends up on the PA of the SIP domain. All things published must end up in this central PA for a domain otherwise is impossible to find the information. >> Sending a Publish is very easy with a few lines of code even netcat would >> do if you do not want to use a full sip stack. > > Yes, I implemented the same when I did a XCAP server. However, you > cannot know how the client will subscribe to changes in its documents. Can't you force from the server to what the client can subscribe? Full or partial updates? Adrian _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
