On Wed, Jun 05, 2002 at 05:06:44PM -0700, Justin Erenkrantz wrote: > Ideally, lessons learned here in serf can drive any changes in > httpd-2.1. It seems that input side of things in httpd-2.0 has > largely been ignored - something that absolutely can't be ignored > for a client library like the mythical serf.
Definately. Especially for things like the proxy which have to deal with both the server and client sides of HTTP. I don't want to reinvent the wheel though, and there are many good client-side HTTP libraries out there. I'd rather see us identify problems (like the one in flood) that we want to solve. I think having concrete problems will help drive development here. > However, the biggest problem, IMHO, is the level of abstraction > we want to have in serf. I know Aaron and I have talked about it, > but I'm not sure that anyone came to an agreement here. I also > know that Aaron has widly different views about the abstraction > of things versus what is in httpd-2.0. So, that may be worth > discussing first (I'm not terribly sure if he's written up email on > this)... For starters, do we use the buckets and brigades from > apr-util? I wouldn't say "wildly" different, but indeed different. :) There was some talk recently both here and on [EMAIL PROTECTED] (not to mention IRC), but I still feel it is too early for me to start talking design until I get a better grasp of the kinds of problems I'd like to solve WRT filters and abstract I/O. Hopefully I'll have more solid ideas that we can talk about as OSCON and even better at the hackathon. -aaron
