Issue #362: We need "request" and "response" objects after all

While writing a converter for a web analysis tool, it became clear to me that using  threadFlow.immutableState  to hold web request headers was  not  sufficient to meet the needs of these tools. So I filed
Issue #362 , “Defined request and response objects.”

The issue explains the rationale in more detail, and presents a proposal. The proposal is  non-breaking . It recapitulates the pattern we’ve used previously for logical locations and addresses: using  cached objects  to reduce repetition of request and response objects, and making requests and responses  externalizable  to reduce file size.

I am going to produce a change draft and optimistically merge it into the provisional draft. I don’t actually think this is a controversial proposal; I just wish I had understood earlier how important it was.

My original goal was to have everything merged by end of day Tuesday (today) to give everybody a full week to review the final version. At this point I will miss that goal, but only by about half a day. Despite the seeming size of this  change, it’s quite similar to text I’ve written many times before, so I expect to be done no later than noon tomorrow. I’ll let you know as soon as the draft is available.

Thanks,
Larry