Before one moves on to what I was told was the real topic of this thread...
> "Kornél Pál" > however this topic is about using > HTTP API in Apache HTTPD. First let's clear up some ideas. :) Forgetting about logging for now. > WRowe > I thought the entire point was that it It being the HTTP.SYS service... > was smart enough to act like a > squid-like low level in-kernel cache? > If not I'm disappointed :) > Yes I believe it is... So does everyone agree with the below: That once a file is HTTP.SYS cached (for now we do not care how or why only that the file is cached), that once a file is cached in the service cache of HTTP.SYS, from there on until the cached file has reached it's set timed out period or the HTTP.SYS is stopped, then only the HTTP.SYS service will handle the file and send the file, as a cached response (no other process is needed, whether that process be IIS or Apache or a .NET Framework http aware process)? Agreed? Now clearing up other ideas: > "Kornél Pál" > It's a reply to a quotation that said HTTP API > is not a good choice for a "high demand place" > as it lacks a lot of feauters. But the author of this > quotation thought that HTTP API is a web server. And > "Kornél Pál" > HTTP API is not a web server. Correct....usually there is another http aware process involved, but a little FYI: Windows now means .NET Framework... (yes old Windows http ways are still available Winsock and all, but newer http ways are HTTP.SYS and .NET Framework) Yes both old and new can be used together if one does the work..... Anyway this is why I say, with the "newer" Windows ways, (.NET Framework usage), it can be used now (beta) and soon (I hope with the final Windows XP SP2 release, but who knows) as a simple web server. (via .NET Framework) When the .NET Framework class was written, the class includes the code from HTTP.SYS, making HTTP.SYS a .NET Framework callable web server or a HTTP.SYS function caller for another http aware process. Read on.... In .NET Framework (soon out): HttpListener class (uses HTTP.SYS) Defined as a simple web server.... One that can self-host or be hosted by another server (http aware process)... Windows XP SP2 and higher... This is what I meant by "stand alone" ( yes for a quick and "dumb" web server) but, HTTP API by itself ( using C/C++ or PInvoke with .NET Framework without HttpListener) always needs another process, unless serving cached files (put there by another http aware process). So right now I would not use .NET Framework's HttpListener (a HTTP.SYS web server), for a "high demand business" without adding other classes but yes HTTP.SYS is or is not (user's choice) in the .NET Framework, a web server and maybe great for those quick http actions, for say grandpa's pictures and other such quick business needs. (Yes under the covers HTTP.SYS is a separate service combined with others actions to make it a simple .NET Framework web server) So that was the stand alone web server thought.... via .NET Framework... Let it go if you must, but be aware of it. There is a lot going on in .NET Framework, even with (and for) Apache usage, but that is for another thread... Jeff
