Henning Schulzrinne wrote:
The server-based approach has the advantage that the server may have a
better idea what's available, avoiding having to client to try a bunch
of things. (The discovery mechanism addresses that problem to some extent.)
The server based approach is more time and network efficient. I hope
those are important attributes for emergency use cases.
The problem with the server-based approach is that it starts to get
messy if the alternative, second-best answer is a list, not a single
answer. Suddenly, the protocol has to support providing a possibly
lengthy list of services that are all potential substitutes.
What is suppose to happen with a list of services on the user end? I
want sos.fire and I get back a list of sos.utility, sos.scuba-accidents,
and sos.crazy-persons? What am I suppose to do with those?
Ecrit mailing list