A followup thought to this: When updating the list of resources within a resource list, if our goal is to minimize the number of subscriptions to phones created and destroyed, we don't necessarily have to minimize the number of ResourceReference objects we create/destroy because the subscriptions are tied to the ResourceCached objects instead. The trick would be to take the new list of resources and add them to (say) the end of the existing resource list. Siince only one ResourceCached object exists for all the ResourceReference's for a single URI, these additions would not create any new ResourceCached objects (except if a new URI was being added to the list), and so no new subscriptions would be created. Then we could delete from the front of the resource list the original set of ResourceReference objects, again with no change to the set of ResourceCached objects (except for URIs that had been deleted from the list).
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/
