httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@covalent.net>
Subject Re: [PATCH] mod_ssl input filtering...
Date Fri, 05 Oct 2001 22:34:41 GMT
From: "Justin Erenkrantz" <jerenkrantz@ebuilt.com>
Sent: Friday, October 05, 2001 4:50 AM


> Ideally, we almost need another mode type that says, "I want you to 
> block until the first packet received and then return that to me."
> This is along the lines of what Madhu was talking about earlier.
> And, I now see the light.  =)

Aaron and I were chatting about this in stream-of-consiouness mode,
let me boil down our collective lightbulb.

We actually have two number;

* minimum required bytes (blocking) to return
  [could be 0 - don't care]

* maximum bytes (non-blocking) that can be accepted
  [could be 0 - no limit]

Now PLEASE understand that maxbytes 0 (originally, the -1 idea) doesn't
say 'read everything from this socket' --- it leaves the best-fit for
the underlying filter to decide.  If core wants to give back an even
number of IP frames, then fine.  If SSL wants to give back an even
number of decoded SSL packets, also fine.  It will not mean read until
EOS, ever.  It's up to the underlying filter to decide what is optimal
for max 0, without allocating a bunch of otherwise useless frame buffers.

And the more that I look at this, the more we need a push-back model,
because the scope of 'this' filter doesn't live as long as the parent
filter (with request and connection scopes, respectively.)

Bill








Mime
View raw message