httpd-test-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacek Prucia <jacek.pru...@7bulls.com>
Subject where to start?
Date Wed, 04 Sep 2002 12:01:15 GMT

Right now flood starts always with Bingo farm. This is just simply
hardcoded. I would like to change that and additionally add getopt
parsing to flood. We could have arguments to run particular farmer
(-f/--farmer), particular farm (-r/--farm) and so on (no
collective/megaconglomerate yet). What if there's no command line
options, but only plain config file? I think we schould do as listed:

1. check for first megaconglomerate, step 2 if not found
2. check for first collective, step 3 if not found
3. check for first farm, step 4 if not found
4. check for first farmer, step 5 if not found
5. bail out

Since there's no collective/megaconglomerate yet, I think I'll just
start with point 3. Additionally we have farm as 'top structure', but a
lot of error messages refers to profile. I think we might tweak those
error messages a bit.

I've picked such small issue on purpose. I think we might hold off
serious changes for 2 reasons:

1. We might have el-kabong in apr-util which could be *VERY* usefull
(new postprocess func with simple wildcards instead of complex regexps,
automatic requesting of <img>'s & <embed>'s from current HTML response
and more)

2. There's some code in apr-serf (aye! :) and it looks like it has those
desired filters out-of-the-box. I have no idea how far is apr-serf from
basic usability, but since flood doesn't have huge user base, we could
wait for apr-serf to mature a little, and rewrite flood to use filters.

regards,
-- 
Jacek Prucia
7bulls.com S.A.
http://www.7bulls.com/


Mime
View raw message