On 24 Apr 2001 [EMAIL PROTECTED] wrote: > dougm 01/04/23 22:10:41 > > Modified: src/modules/perl modperl_types.h > Log: > allow MP_IOBUFSIZE to be -D defined That's the buffer size you have mentioned in your reply to my dual setup question? This solves the outgoing data server tieing. What about incoming traffic. Can we do the same for let's say files uploaded from slow clients? So the data gets buffered somewhere, while Perl interpreter is not used? Basically the idea is not to invoke the Perl interpreter before a certain amount (or all of it) of data has been read. > Revision Changes Path > 1.37 +6 -4 modperl-2.0/src/modules/perl/modperl_types.h > > Index: modperl_types.h > =================================================================== > RCS file: /home/cvs/modperl-2.0/src/modules/perl/modperl_types.h,v > retrieving revision 1.36 > retrieving revision 1.37 > diff -u -r1.36 -r1.37 > --- modperl_types.h 2001/04/19 21:26:35 1.36 > +++ modperl_types.h 2001/04/24 05:10:40 1.37 > @@ -1,10 +1,12 @@ > #ifndef MODPERL_TYPES_H > #define MODPERL_TYPES_H > > -#ifdef AP_IOBUFSIZE > -# define MP_IOBUFSIZE AP_IOBUFSIZE > -#else > -# define MP_IOBUFSIZE 8192 > +#ifndef MP_IOBUFSIZE > +# ifdef AP_IOBUFSIZE > +# define MP_IOBUFSIZE AP_IOBUFSIZE > +# else > +# define MP_IOBUFSIZE 8192 > +# endif > #endif > > /* aliases */ > > > > _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/ http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
