On Wed, Jun 05, 2002 at 04:13:01PM -0700, Greg Stein wrote: > As I've mentioned before, I think somebody ought to just sit down and write > out what the header should be for the project. Once we have a set of APIs > "on paper", so to speak, then we can use it as a focal point for discussion.
Maybe easier said than done. Perhaps we don't quite understand what kinds of problems we'd like to solve here. I for one would like to solve some problems in flood using apr-serf, the most interesting being abstract I/O (we need to do client-side verification of returned data in a way that is modular so that different verification pieces can be added and removed at will). This is of course a huge goal, so it might make more sense to start focusing on smaller goals and work our way up. What client-side utilities are missing from APR that are necessary here? Do we need a killer-app (maybe flood is that app) to drive this? Can/should we merge some code that is already out there, like apreq? Where do we draw the line between kitchen sink and a "must have"? -aaron
