________________________________________ From: Jean-Hugues Royer [[email protected]]
When the RLS receives two partial non consecutive notifications (ie. version="10" & version="12", version="11" missing) by RFC4235 it should refresh its subscription to get the full state. As far as I saw the RLS doesn't refresh it, resulting in a temporary inaccurate status of the extension for the clients. _________________________________________ That is the same effect as we've discussed before: In the 'full' events, the subscriber to the event list gets the last update as it was received from the source(s). In particular, the RLS does not attempt to interpret version numbers. This does limit the usefulness of the "full" events, or at least, puts quite a burden on the subscriber who is interpreting them. But RFC 4662 does not mention that the resource list aggregator should attempt to interpret the events. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
