I am starting work on XX-7389, "Subscribe Server should respond 404 when SUBSCRIBE does not address an implemented resource". There is an open design question regarding how the Subscribe Server should determine if a resource exists or not. During normal operation, the application code will have published content for every resource that exists, which makes the decision whether or not to respond 404 rather easy. But during startup, the Subscribe Server has no reliable guide to which resources are implemented and which are not (since the application code hasn't told it yet).
One solution to this problem is to ignore it -- if the application hasn't provided content yet, respond 404, and assume that the subscriber will retry later, by which time the content will have been provided. Ideas? 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/
