On Mon, 2010-01-18 at 09:15 -0500, Beeton, Carolyn AVAYA (CAR:9D60) Sounds good to me too. Just to be clear, the mechanisms we have in > place to persist subscriptions will now only apply over unclean > shutdowns of the SubscribeServer (crashes). On a clean shutdown, all > subscriptions will be terminated, and removed from the persisted > subscriptions list. Is this correct?
I hadn't thought about persistence. But it seems to me that the right way to handle that is as an alternative type of SipSubscribeServer::shutdown(). ::shutdown() will get an argument which describes how the subscriptions are to be shut down, and one option will be "Don't tell the subscriber anything, since the re-execution of this server will continue the subscriptions." That option will cause the subscriptions to remain in the persistent database. The other options, which notify the subscriber that the subscription is ending, will remove entries from the persistent database. Those choices seem to produce the desired effects. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
