dgaudet 98/03/07 22:17:57
Modified: docs stacked_io
Log:
more comments
Revision Changes Path
1.3 +12 -1 apache-2.0/docs/stacked_io
Index: stacked_io
===================================================================
RCS file: /export/home/cvs/apache-2.0/docs/stacked_io,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- stacked_io 1998/03/08 06:07:50 1.2
+++ stacked_io 1998/03/08 06:17:56 1.3
@@ -185,6 +185,13 @@
Unix, it would be a pair of file descriptors); the second holds the
void * pointer passed to all user-supplied functions.
+[djg: I don't think I really agree with the distinction here between
+the bottom and the other filters. Take the select() example, it's
+valid for any layer to define a fd that can be used for select...
+in fact it's the topmost layer that should really get to make this
+definition. Or maybe I just have your top and bottom flipped. In
+any event I think this should be part of the filter structure and
+not separate.]
The BUFF structure
@@ -540,4 +547,8 @@
are done via flags and options will be done by attaching appropriate
filters instead (eg. chunking).
-
+[djg: I'd like to consider filesystem metadata as well -- we only need
+a few bits of metadata to do HTTP: file size and last modified. We
+need an etag generation function, it is specific to the filters in
+use. You see, I'm envisioning a bottom layer which pulls data out of
+a database rather than reading from a file.]
