some new branches

Hi
    I've found that the rbcollins_filters branch is getting a bit of attention (based on the list archives cropping up in search
engines I believe).

Anyway, as I am really working on four things in parallel there, I'm creating a couple of new branchs on sourceforge (now they've
fixed up todays CVS glitch [There were a number of faults reported]).

The branches are:

* acl_work, for extensions/bugfixes/alterations to acl capabilities in general (ie the new rep_mime_type acl & test in client_side
has an issue with reponses with no body that I'm going to create a new patch for HEAD).
* generic_modules, for working on generic module support. In here I'm hoping things like generic parsing code, plugin capabilities,
dlopenable modules, the framework really to plug modules without rewriting the same shell script and config routine 50x.
* content_processing, which will have the framework that Joe and Moez are utilising for their current project. This framework is
needed for transfer encoding as well -
* te & te_modules already exist, but I will start merging down to them from the content_processing and generic_modules branch rather
than coding into te directly.

As soon as I've split it all up, and tracking correctly, I plan to get rid of rbcollins.filters as a private branch. Secondly the
work to get partial responses cacheable flows on from the work I am doing to the store interface (not the guts, just what the
external API,) by disjointing the client_side and server side requests a bit more cleanly. So I expect to pick that up again in the
near future, and probably make it dependant on one or more of the above branches...

Questions: am I overlapping on any other branch to the degree that I shouldn't create a new branch and instead should work in that
branch?
Any other issues/suggestions/comments?
Received on Tue Feb 13 2001 - 06:15:53 MST