stas 2003/09/16 13:59:24
Modified: src/docs/2.0/user/handlers filters.pod
Log:
remove old para
Submitted by: Finn Hakansson <[EMAIL PROTECTED]>
Revision Changes Path
1.34 +22 -5 modperl-docs/src/docs/2.0/user/handlers/filters.pod
Index: filters.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/handlers/filters.pod,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -u -r1.33 -r1.34
--- filters.pod 18 Jul 2003 10:42:48 -0000 1.33
+++ filters.pod 16 Sep 2003 20:59:24 -0000 1.34
@@ -312,11 +312,6 @@
----------------------
1st eos
-The EOS bucket may be attached to the last bucket brigade with the
-data, rather than be sent in its own brigade, therefore filters should
-never make an assumption that the EOS bucket is arriving alone in a
-bucket brigade.
-
Notice that the EOS bucket may come attached to the last bucket
brigade with data, instead of coming in its its own bucket brigade.
Filters should never make an assumption that the EOS bucket is
@@ -2534,6 +2529,28 @@
=head1 Writing Efficient Filters
META: to be written
+
+[
+
+As of this writing the network input filter reads in 8000B chunks (not
+8192B!), and making each bucket 8000B in size, so it seems that the
+most efficient reading technique is:
+
+ use constant BUFF_LEN => 8000;
+ while ($f->read(my $buffer, BUFF_LEN)) {
+ # manip $buffer
+ $f->print($buffer);
+ }
+
+however if there is some filter in between, it may change the size of
+the buckets. Also this number may change in the future.
+
+Hmm, I've also seen it read in 7819 chunks. I suppose this is not very
+reliable. But it's probably a good idea to ask at least 8k, so if a
+bucket brigade has < 8k, nothing will need to be stored in the
+internal buffer. i.e. read() will return less than asked for.
+
+]
[
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
