From: "Rodent of Unusual Size" <[EMAIL PROTECTED]>
Sent: Thursday, March 01, 2001 1:23 PM
> Consider the case of an existing (1.3) module that uses
> ap_r*. The author's goal is to do as little as possible
> to make it work under 2.0. It sounds as though the OLD_WRITE
> solution will do this; he can leave all his content-related
> calls along, and just upgrade the hooks. The macro option
> requires him to learn about bucket brigades.
>
> Is that correct?
Nak. ap_r* fn's would create an r->bb for him, and shuttle all of
his ap_r* calls into that brigade.
Only the _cross-mechansim_ author needs to know that if he _chooses_
to create is very own brigade, it isn't in sync with any ap_r* calls
he might make, unless he then stuffs it in r->bb (presuming r->bb wasn't
created... hmmm, sounds like an ap_set_request_brigade() semantic is in
order to be _certain_ that user's don't directly hork up an already
created r->bb)
Bill
