I really like being able to do: write(8K)*n + flush().
+1 on adding a FlushPackets config option set to off by default.
Thank you Mladen and Jean-Frederic.
Jean-Jacques
>>> [EMAIL PROTECTED] 5/18/2005 7:41 AM >>>
Henri Gomez wrote:
> good idea.
>
> Which state by default ?
off (-FlushPackets)
Henri Gomez wrote:
good idea.
Which state by default ?
off (-FlushPackets).
2005/5/18, jean-frederic clere <[EMAIL PROTECTED]>:
Mladen Turk wrote:
jean-frederic clere wrote:
Mladen Turk wrote:
I think on/off is enough - Think of the questions nnn will bring in
user list -
So how about to just add
good idea.
Which state by default ?
2005/5/18, jean-frederic clere <[EMAIL PROTECTED]>:
> Mladen Turk wrote:
> > jean-frederic clere wrote:
> >
> >> Mladen Turk wrote:
> >>
> >> I think on/off is enough - Think of the questions nnn will bring in
> >> user list -
> >>
> >
> > So how about to just
Mladen Turk wrote:
jean-frederic clere wrote:
Mladen Turk wrote:
I think on/off is enough - Think of the questions nnn will bring in
user list -
So how about to just add the flag to JkOptions like +FlushPackets?
+1.
Regards,
Mladen.
jean-frederic clere wrote:
Mladen Turk wrote:
I think on/off is enough - Think of the questions nnn will bring in user
list -
So how about to just add the flag to JkOptions like +FlushPackets?
Regards,
Mladen.
-
To unsubscribe, e
Mladen Turk wrote:
jean-frederic clere wrote:
Not sure what you mean by that. Like a generic callback?
Yes to able to flush the same way we write.
OK, makes sense.
If 'JkFlush Off' is used a single ap_rflush will be issued
when all the data is send.
Then why not using 'JkFlush Off' as default beha
jean-frederic clere wrote:
Not sure what you mean by that. Like a generic callback?
Yes to able to flush the same way we write.
OK, makes sense.
If 'JkFlush Off' is used a single ap_rflush will be issued
when all the data is send.
Then why not using 'JkFlush Off' as default behaviour?
That makes se
Mladen Turk wrote:
jean-frederic clere wrote:
Mladen Turk wrote:
JkFlush (On|Off|size) with On as default for each packet write.
That way we'd be able to flush after each write, flush after each
'size' bytes or not flush at all.
Won't it be better to have a ws_flush()?
Not sure what you mean by tha
jean-frederic clere wrote:
Mladen Turk wrote:
JkFlush (On|Off|size) with On as default for each packet write.
That way we'd be able to flush after each write, flush after each
'size' bytes or not flush at all.
Won't it be better to have a ws_flush()?
Not sure what you mean by that. Like a generic c
Mladen Turk wrote:
Jean-Jacques Clar wrote:
re-sending :
Am I missing details?
Calling ap_rflush() at the end of ws_write() in mod_jk.c is causing me
problems when doing downloads from the server to a client.
Performance degradation and, less importantly, memory usage, are the
problems.
Seems
Jean-Jacques Clar wrote:
re-sending :
Am I missing details?
Calling ap_rflush() at the end of ws_write() in mod_jk.c is causing me
problems when doing downloads from the server to a client.
Performance degradation and, less importantly, memory usage, are the
problems.
Seems we are the only mod
re-sending :
Am I missing details?
Calling ap_rflush() at the end of ws_write() in mod_jk.c is causing me
problems when doing downloads from the server to a client.
Performance degradation and, less importantly, memory usage, are the problems.
During calls to ap_rwrite() in ws_write, a brig
12 matches
Mail list logo
