145N/AFor obvious compatibility reasons, the over-the-wire protocol needs to be
145N/Aversioned. Since we're using HTTP, it makes sense to simply version the
145N/AThe scheme is pretty simple:
145N/Awhere "version" is a simple integer.
145N/A - Are there operations where we don't want to require a version?
145N/A - Is there a use for a "300 Multiple Choices" HTTP return code?
145N/A - If we always try the client-optimal version first and then back off
145N/A linearly, we'll want to cache the version that succeeded so we don't
145N/A spend all of our time trying versions that don't exist.
145N/A - Alternatively, we can call "versions" to find out what versions the
145N/A server supports for each operation, and cache that.