As to the browser version incompatibility argument, aren't we talking about a single browser here? The XO? The school server isn't serving a random population of browsers. (Admittedly there might be a few non-XO machines, but I assume in most cases not many).<br>
<br>Similarly, we know exactly what the major web components are to be resident on the school server, and the reverse proxy (if one were to be used) would be mediating traffic between these and the XOs. So their behavior regarding caching headers would be easily determined. Even so it seems as though a reverse proxy only has applicability to country servers or in the case of school servers, to a redundant configuration at a large school, e.g. Mongolia. And then, what is really wanted is a load balancing function. <br>
<br>On the other hand, a forward proxy serves a useful purpose mediating between the school server and a slow/intermittent web connection. Am I missing something?<br><br><br><div class="gmail_quote">2008/3/8 Ivan Krstiæ <<a href="mailto:krstic@solarsail.hcs.harvard.edu">krstic@solarsail.hcs.harvard.edu</a>>:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Mar 9, 2008, at 1:04 AM, Martin Langhoff wrote:<br>
> But you can't count on the upstream project to be producing good<br>
> caching headers - they wouldn't be able to use it on the Internet.<br>
<br>
<br>
</div>This is far too strong a statement to stand without qualification.<br>
It's one thing to say browsers might ignore cache control headers and<br>
re-issue requests they shouldn't, causing unnecessary traffic. It's<br>
another thing entirely to say that you believe applications should<br>
intentionally omit cache control headers because it might break the web.<br>
<br>
In a previous life, I built a non-trivial chunk of backend<br>
architecture for one of the largest websites in existence. To my<br>
knowledge, we were never burned by using cache control headers. It's<br>
certainly possible you can convince me this is a bad strategy, but I'm<br>
trying to make sure you understand there's a burden of proof here;<br>
shunning standards on account of hand-waving about things that might<br>
hypothetically break is a bad idea, and doubly so when building a new<br>
platform.<br>
<font color="#888888"><br>
--<br>
Ivan Krstiæ <<a href="mailto:krstic@solarsail.hcs.harvard.edu">krstic@solarsail.hcs.harvard.edu</a>> | <a href="http://radian.org" target="_blank">http://radian.org</a><br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Server-devel mailing list<br>
<a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/listinfo/server-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>"Always do right," said Mark Twain. "This will gratify some people and astonish the rest."