| 1) You don't need to poll atime descriptors. Neither do you need to use watch descriptors (although I don't understand your argument about them). You just need a way to tell the server that you updated a page. It might have been a good point if we were discussing specific implementations. 2) Are you saying that it was a completely irrelevant thing to mention in your list of problems with generating static files to begin with? If so, I agree. 3) Whether you're right or wrong (I can't tell at this point, and I won't simply decide on either until there are numbers to prove it), you are arguing on the basis of very limited and somewhat unlikely scenarios. I could argue on the basis of having very complex templates and page logic to generate extremely small pages, but I don't since I realize that it's not very likely to happen. Elephants again... 1) No. If your use case is such that your static page contains the same information what your dynamically generated equivalent would (and no one is arguing for using static pages if this isn't possible), you don't need additional round trips. 2) If all data you need to render to a page is static, you could easily go from one roundtrip to none. Let's bring another animal into the room: With static files, you can enjoy the luxuries of very expressive languages with slow runtimes to build your pages, without any performance impact on serving them. Generating dynamic pages in a way that will even come close to serving static files in terms of performance is going to mean spending more effort than is viable for most projects. |