How to install on Windows?

[Wolfgang Strobl]

"Gregory (Grisha) Trubetskoy" <grisha at ispol.com>:

>On Fri, 6 Dec 2002, Wolfgang Strobl wrote:
>
>> "Gregory (Grisha) Trubetskoy" <grisha at ispol.com>:
>>
>> >> The problem _I_ am struggling with right now is how to write an output
>> >> filter with mod_python for processing very large files, without reading
>> >> the whole file into memory. Any suggestions?
>> >
>> >An apache *filter* has no notion of file size,
>>
>> That's fine with me. Replace "file" by "conent to be filtered".
>>
>> >it just processes data as
>> >it is written out and has no control over how much data is passed through
>> >it.
>>
>> I'm asking wether it reads the whole input into memory before giving it
>> to my output filter, or perhaps collects all the written output before
>> actually delivering it, and how to avoid that behaviour.
>
>This depens on what "it" is, and "it" can be a number of things, it could
>be a standard apache handler that reads a static file and sends it out, or
>it could be output from a cgi script. 

"It" is a file, of course. See above.   


>But you can't control how much is
>read and written from within a filter, you are at "it"'s mercy.

Alas, this doesn't answer my question. How does the standard apache
handler that reads static files from the file system behave? Or better:
what it the standard practice for processing content from the file
system which is large in relation to the available main memory in
apache filters, and how does this practice translate to mod_python? 

Anyway, thanks for the pointers.


-- 
Wir danken für die Beachtung aller Sicherheitsbestimmungen