> What you're describing is commonly called a Registry ;) and is both
> unnecessary and unhelpful in this case. If you have 3 end points for
> version 1.0 and 3 end points for version 1.1 and 3 end points
> for version
> 1.2, then you have to return 9 different
From a client's perspective that sounds ideal - there is a single
published end point which gives you all the information you need to
decide which protocol/version you should use.
As server developer I can add a new protocol/version knowing that
clients will pick this up automatically without me having to send around
> but practically
> identical explain
Which is why one of the proposals was to repeat serverInfo within a
single Explain rather than multiple Explain records.
Even so, I suspect most servers will generate the Explain information
automatically so there is no real duplication of configuration
information needed at the server end
> Uhhh... No thanks. If you have different end points, each end
> point has its own explain operation which does exactly what
> it says on the
> tin. It explains how to use this particular service.
But now I still have nine different but practically identical explain
records (albeit at different endpoints) but in addition have to
configure my client with nine different endpoints so that it can inspect
them all to determine which protocol/version to use! That sounds even
more unhelpful to me!