On Sat, 2010-01-16 at 12:51 -0500, Dale Worley wrote: > General idea: > > If a resource name has no content recorded for it, attempts to subscribe > to that resource name are rejected with a 404 response. > > If the content for a resource is removed, any existing subscriptions to > that resource will be terminated. > > Specifics: > > SubscribeServer will test new SUBSCRIBEs to see if content is provided > for the given resource name. As is true now, content can be provided by > being specifically published for that resource name, provided by a > "default content" function, or provided by being published as default > content for all otherwise unknown resources. > > The "unpublish" method will be renamed and its intention extended to > "delete" the specified resource. New SUBSCRIBEs to the resource will be > rejected with 404. All existing subscriptions to the resource will be > terminated. The termination NOTIFY will include the > previously-published content (to avoid confusing the subscriber). As is > true now, the termination NOTIFY can be suppressed or not, and will be > extended to provide a "reason" value per RFC 3265 (to work better in HA > environments). > > Stopping the SubscribeServer will terminate all existing subscriptions, > and will provide the alternative terminations that can be obtained with > unpublish(). > > Correct handling of various cases when specific content is removed for a > resource but default content still applies to it. > > Correct handling when no content for an existing resource is an > acceptable media type for the subscriber. > > Comments?
Sounds good. _______________________________________________ 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/
