Check the code we built for managing these exceptions: http://sipsimpleclient.com/wiki/SipMiddlewareApi#XCAPsupport
Your bug reports are welcome. Adrian On Sep 10, 2010, at 8:05 PM, Iñaki Baz Castillo wrote: > 2010/9/10 Adrian Georgescu <[email protected]>: >> Syncing buddy lists by using SIP protocol is something you should think >> about more carefully before even attempting it. > > SIMPLE (or OMA) already defines it: > > 1) The user subscribes to changes in its resource-lists document. > > 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. 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. Or send a rpc command from the XCAP server to the Presence Agent, you can do this in many different ways depending on what sip presence agent you have available. > 3) The user receives NOTIFY with incremental changes in its contactlist. > > I do know that in step 1 the user could request to be notified just > with the new document version so later it retrieves it entirely via > XCAP ("bandwith efficient"). But what I mean is that IETF/OMA already > defines how a SIP UA can receive incremental changes in its > contactlist by means of SIP notifications. Are IETF and OMA also wrong > as me? :) > > > -- > Iñaki Baz Castillo > <[email protected]> > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
