On Fri, 21 Oct 2016, Alex Xu wrote:
Also think 404 is right at here. If you return 406 and it is a signal that
if you used a different microversion the situation could be different, the
thing will become strange when we raise the acceptable min_version someday.
Thanks, yeah, what you and Ed ha
2016-10-19 0:58 GMT+08:00 Ed Leafe :
> On Oct 18, 2016, at 11:01 AM, Chris Dent wrote:
> >
> > If the requested microversion is greater than the maximum, a 404 still
> > makes some sense (no mapping _now_), but a 406 could as well because it
> > provides a signal that if you used a different micr
On Oct 18, 2016, at 11:01 AM, Chris Dent wrote:
>
> If the requested microversion is greater than the maximum, a 404 still
> makes some sense (no mapping _now_), but a 406 could as well because it
> provides a signal that if you used a different microversion the
> situation could be different and
On Tue, 18 Oct 2016, Chris Dent wrote:
If the requested microversion is greater than the maximum, a 404 still
makes some sense (no mapping _now_), but a 406 could as well because it
provides a signal that if you used a different microversion the
situation could be different and the time represen
I'm in the midst of writing the microversion handling code for the
placement API and I've stumbled across a situation that I'm not sure
how I should resolve. This is not necessarily something that someone
should do with microversion, but since it is possible, I'd like to
make the code behave in t
