Notification required because of subscription refresh >-----Original Message----- >From: sip-implementors-boun...@lists.cs.columbia.edu >[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On >Behalf Of Alex Balashov >Sent: Tuesday, January 20, 2009 4:53 PM >To: Iñaki Baz Castillo >Cc: sip-implementors@lists.cs.columbia.edu >Subject: Re: [Sip-implementors] RFC 4235 - Why is needed >"version" in NOTIFY XML > >Iñaki Baz Castillo wrote: >> 2009/1/20 Victor Pascual Ávila <victor.pascual.av...@gmail.com>: >>> On Tue, Jan 20, 2009 at 12:14 PM, Alex Balashov >>> <abalas...@evaristesys.com> wrote: >>>> If so, what are the formal reasons for re-sending a NOTIFY with >>>> unchanged event package data? >>> I guess time-driven notifications >> >> You mean that a notifier could send periodic NOTIFY even if no state >> change has occurred, is it? > >It could, certainly, but what would be the purpose of that? > >I thought a key architectural premise -- at least, of presence >and dialog-related notification schemes -- is that NOTIFYs go >out only when there is something meaningful to update? > > >-- >Alex Balashov >Evariste Systems >Web : http://www.evaristesys.com/ >Tel : (+1) (678) 954-0670 >Direct : (+1) (678) 954-0671 >Mobile : (+1) (678) 237-1775 >_______________________________________________ >Sip-implementors mailing list >Sip-implementors@lists.cs.columbia.edu >https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >
_______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
