On Thu, Jul 14, 2011 at 12:30 PM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> On 07/14/2011 12:01 PM, Philip Martin wrote:
>> It's possible to setup a 1.7 write-through proxy to a 1.6 master.
> It's also a really bad idea.
I think that opinion is overly extreme. While it is certainly true
that you cannot just mix any two server versions, a blanket statement
that it is a bad idea to mix versions is not really true either.
People cannot always update every server at the same time so I do not
think this can or should be our position.
I plan on supporting 1.7 proxies with 1.6 masters by setting the
directive to not advertise the V2 protocol in this situation. I am
comfortable doing this and do not see any problems with it. Do you?
Could a proxy do some kind of negotiation with the master on startup
and then use that for its negotiations with clients? In other words,
it seems like a proxy could self-configure itself and how it responds
to the OPTIONS request based on what it knows about its master. In
the example above, it could turn off V2 itself if it knows the master
does not support it.
Received on 2011-07-14 18:59:18 CEST