On Wed, Sep 04, 2002 at 02:01:15PM +0200, Jacek Prucia wrote: > 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:
Yeah, APR should have all of the getopt bits already available. But, I would definitely prefer that we not overdo command-line options. (The one killer command line argument would be --no-delay - which shuts off the delays.) > 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 I'm not 100% sure we can go to step 4. Would we just say that it is one farmer? > 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. Fair enough. > I've picked such small issue on purpose. I think we might hold off > serious changes for 2 reasons: Baby steps. =) > 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) Well, el-kabong is kind of political limbo, so I wouldn't wait for it to get checked-in. If you do want to use it and are willing to code up patches for it, we may be able to use that as a stick to find el-kabong a home (and you'd need to acquire the source to it too). > 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. serf is probably a while off. There's something in its repository, but we still haven't finished out its design yet. There's a lot more that we need to think about. But, feel free to jump into the discussions over on serf-dev@ if you like. We need more people thinking about it. =) -- justin
