- From: Roy T. Fielding <fielding@kiwi.ICS.UCI.EDU>
- Date: Fri, 19 Nov 1999 22:34:34 -0800
- To: "Sean Lyndersay (Exchange)" <seanlynd@exchange.microsoft.com>
- cc: w3c-dist-auth@w3.org
>Funny you should bring this up. Exchange Server has had to deal with the >problem in our implementation and decided to solve it with a new header, >"Translate" on GET requests, which takes the values "t" and "f" and >defaults to "t" if omitted. Well, congratulations, you chose the worst possible design choice. By using a header field, you have excessively complicated the caching algorithm for all resources on your server. If it isn't sending "Vary: Translate" on every response, your server is not HTTP/1.1 compliant. Next time, use a "source" property that contains a list of URI that make up the sources for a particular resource. Authoring requests are of negligible significance for round-trip latency concerns, so spend the round-trip where it has the least performance impact rather than constipating the normal operation of your server. ....Roy
Received on Saturday, 20 November 1999 01:34:39 UTC