You are viewing a plain text version of this content. The canonical link for it is here.
Posted to serf-dev@apr.apache.org by Rodent of Unusual Size <Ke...@Golux.Com> on 2002/05/09 05:45:25 UTC
[STATUS] (apr-serf) Wed May 8 23:45:25 EDT 2002
APR-SERF STATUS: -*-text-*-
Last modified at [$Date: 2001/10/24 20:02:29 $]
Release:
RELEASE SHOWSTOPPERS:
We need code. This project's goal is to create an http
client library.
* web pages (go to apr-site)
* decide on prefix
serf_ : +1 Greg, Aaron
aps_ :
apr_serf_ :
* decide on layout of the repository (e.g. subdirs)
Greg thinks: prolly the following: /build, /include, /docs, /test,
/core, and some for high-level items (maybe /filters
and /utils)
* set up config/build structure based on apr-util
(take this opportunity to simplify again; hopefully to fold these
simplifications back into apr(-util))
* release scripts (in /build) (and a how-to-release.txt in docs/)
* turn docs/roadmap.txt into a real API/implementation design doc
(at least far enough such that we can generate .h files and begin
coding from there)
RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
next steps (was: [STATUS] (apr-serf) ...)
Posted by Greg Stein <gs...@lyra.org>.
On Fri, May 10, 2002 at 05:56:42PM -0700, Ian Holsman wrote:
> Greg Stein wrote:
>...
> > IMO, our next step for apr-serf is to start writing the serf.h header file.
>
> have we actually come to a consensus on how serf is to be structured?
>
> should we come to a brief consensus on how we think this is going to
> work before writing the headers? (ie flesh out the roadmap a bit more)
I think that we're reasonably close enough that beginning a header file is
required so that we have something constructive to talk about and refer to.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Re: [STATUS] (apr-serf) Wed May 8 23:45:25 EDT 2002
Posted by Ian Holsman <Ia...@apache.org>.
Greg Stein wrote:
> On Wed, May 08, 2002 at 09:36:19PM -0700, Aaron Bannert wrote:
>
>
> I think the URL utilities would go into apr-util. We have a "uri" section in
> there specifically for that stuff.
>
> apr-serf would depend upon both apr and apr-util.
>
> IMO, our next step for apr-serf is to start writing the serf.h header file.
>
have we actually come to a consensus on how serf is to be structured?
should we come to a brief consensus on how we think this is going to
work before writing the headers? (ie flesh out the roadmap a bit more)
> Cheers,
> -g
>
Re: [STATUS] (apr-serf) Wed May 8 23:45:25 EDT 2002
Posted by Greg Stein <gs...@lyra.org>.
On Wed, May 08, 2002 at 09:36:19PM -0700, Aaron Bannert wrote:
> On Wed, May 08, 2002 at 11:45:25PM -0400, Rodent of Unusual Size wrote:
> > APR-SERF STATUS: -*-text-*-
>
> Ok, this is the 14th one of these in a row. I'm just as much to blame
> as anyone else for the stalemate. :) I have been brainstorming how I
> think the filter semantics should work, and hopefully soon it will make
> enough sense to write up here. Until then, should we start getting some
> support functionality in place? Perhaps it would be useful to import
> various URL utilities to apr-serf?
I think the URL utilities would go into apr-util. We have a "uri" section in
there specifically for that stuff.
apr-serf would depend upon both apr and apr-util.
IMO, our next step for apr-serf is to start writing the serf.h header file.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Re: [STATUS] (apr-serf) Wed May 8 23:45:25 EDT 2002
Posted by Aaron Bannert <aa...@clove.org>.
On Wed, May 08, 2002 at 11:45:25PM -0400, Rodent of Unusual Size wrote:
> APR-SERF STATUS: -*-text-*-
Ok, this is the 14th one of these in a row. I'm just as much to blame
as anyone else for the stalemate. :) I have been brainstorming how I
think the filter semantics should work, and hopefully soon it will make
enough sense to write up here. Until then, should we start getting some
support functionality in place? Perhaps it would be useful to import
various URL utilities to apr-serf?
-aaron